Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 61fb0b1cf2b12055bd5863ef89f90613ce0f7b46390aaee4705b0f8ca7754140

Tx prefix hash: a16e1ccd23fcf19ca81f40a3cded3ab24e9e9d11c22b3c397fc74c0d1820ebd1
Tx public key: 781888e8ef5104b0e809e13f8dda895c425ad0ff0629bd129100ed45e52a60f8
Timestamp: 1697173219 Timestamp [UCT]: 2023-10-13 05:00:19 Age [y:d:h:m:s]: 01:097:18:26:06
Block: 868511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331125 RingCT/type: yes/0
Extra: 01781888e8ef5104b0e809e13f8dda895c425ad0ff0629bd129100ed45e52a60f8021100000001e08532b6000000000000000000

1 output(s) for total of 0.813322057000 dcy

stealth address amount amount idx
00: 474511cd04263af370f1f2ea63b50a6d81ddbefb531e45f1b65a9740b65ec2c4 0.813322057000 1323322 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 868521, "vin": [ { "gen": { "height": 868511 } } ], "vout": [ { "amount": 813322057, "target": { "key": "474511cd04263af370f1f2ea63b50a6d81ddbefb531e45f1b65a9740b65ec2c4" } } ], "extra": [ 1, 120, 24, 136, 232, 239, 81, 4, 176, 232, 9, 225, 63, 141, 218, 137, 92, 66, 90, 208, 255, 6, 41, 189, 18, 145, 0, 237, 69, 229, 42, 96, 248, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8