Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcc3e902b12f2a4979d4ece698a8177f5e0602d81290f7c22d00a0a165dcac11

Tx prefix hash: 885ca7552fcf35fb7fa02a70ef3419a03469069244941749713880f0c3928a51
Tx public key: e729e04f41cb89d2a5db6a2c72c6257d4509e9745235dfece02d43f95c2432da
Timestamp: 1681156612 Timestamp [UCT]: 2023-04-10 19:56:52 Age [y:d:h:m:s]: 02:001:23:25:27
Block: 735759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523582 RingCT/type: yes/0
Extra: 01e729e04f41cb89d2a5db6a2c72c6257d4509e9745235dfece02d43f95c2432da02110000000375e3f0e9000000000000000000

1 output(s) for total of 2.239366767000 dcy

stealth address amount amount idx
00: 229b283e42b582a65d79c22218670f72b18562e57700d7f7fa88b1411e140ef5 2.239366767000 1182112 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": 735769, "vin": [ { "gen": { "height": 735759 } } ], "vout": [ { "amount": 2239366767, "target": { "key": "229b283e42b582a65d79c22218670f72b18562e57700d7f7fa88b1411e140ef5" } } ], "extra": [ 1, 231, 41, 224, 79, 65, 203, 137, 210, 165, 219, 106, 44, 114, 198, 37, 125, 69, 9, 233, 116, 82, 53, 223, 236, 224, 45, 67, 249, 92, 36, 50, 218, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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