Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33dc3f2d430bf02162e47f8533170505a66391cc402f16a5ca92633238e849c6

Tx prefix hash: d4025506609975b09b88c0c97d4edfd8462dc59a88ff8a3f09358dace3365c3c
Tx public key: 2be1a9737e8d5b86a278cd27ef7a91a770e2f1d91f8be3dba5f93129340c004d
Timestamp: 1646805141 Timestamp [UCT]: 2022-03-09 05:52:21 Age [y:d:h:m:s]: 03:240:08:12:11
Block: 454485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 949625 RingCT/type: yes/0
Extra: 012be1a9737e8d5b86a278cd27ef7a91a770e2f1d91f8be3dba5f93129340c004d02110000000da8c141c5000000000000000000

1 output(s) for total of 19.147091006000 dcy

stealth address amount amount idx
00: 04e147792fe65e6c8940efe0bca7d044735a7dad61a614c2a4dd5068a8677bf9 19.147091006000 870142 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": 454495, "vin": [ { "gen": { "height": 454485 } } ], "vout": [ { "amount": 19147091006, "target": { "key": "04e147792fe65e6c8940efe0bca7d044735a7dad61a614c2a4dd5068a8677bf9" } } ], "extra": [ 1, 43, 225, 169, 115, 126, 141, 91, 134, 162, 120, 205, 39, 239, 122, 145, 167, 112, 226, 241, 217, 31, 139, 227, 219, 165, 249, 49, 41, 52, 12, 0, 77, 2, 17, 0, 0, 0, 13, 168, 193, 65, 197, 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