Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 590b2e07e1142132bd26c556c3048b2bcbe9bcabfc782c266c314d3b2574abde

Tx prefix hash: 10b39c620a8561d41ee29be198f041dee690ac0c7f423870bb4d1112557fea40
Tx public key: 4f8856fb971d8e9fbcb5e7ac30ac4373259f5e3a198a32818b2b52884c66b663
Timestamp: 1693104817 Timestamp [UCT]: 2023-08-27 02:53:37 Age [y:d:h:m:s]: 01:255:01:23:49
Block: 834744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443452 RingCT/type: yes/0
Extra: 014f8856fb971d8e9fbcb5e7ac30ac4373259f5e3a198a32818b2b52884c66b66302110000000633af99f4000000000000000000

1 output(s) for total of 1.052317247000 dcy

stealth address amount amount idx
00: 89000a3d3cdf7628c2df5ec0efc32661425b0e602af752f5071b2fbc6391b4bc 1.052317247000 1287254 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": 834754, "vin": [ { "gen": { "height": 834744 } } ], "vout": [ { "amount": 1052317247, "target": { "key": "89000a3d3cdf7628c2df5ec0efc32661425b0e602af752f5071b2fbc6391b4bc" } } ], "extra": [ 1, 79, 136, 86, 251, 151, 29, 142, 159, 188, 181, 231, 172, 48, 172, 67, 115, 37, 159, 94, 58, 25, 138, 50, 129, 139, 43, 82, 136, 76, 102, 182, 99, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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