Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f8f7674299ef9d84cf46729c3b83777f57593c057718efced34a939ad0e7c4

Tx prefix hash: ed911d4663cffb178511723c1227cbb2cac1e68d27ec45196a359ec6f7d9b71c
Tx public key: 83e7ae90db09b1fa2a7688a6795e3176330a3df3dadecce922e013ef86ff21fd
Timestamp: 1746364832 Timestamp [UCT]: 2025-05-04 13:20:32 Age [y:d:h:m:s]: 00:233:10:56:49
Block: 1275610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164597 RingCT/type: yes/0
Extra: 0183e7ae90db09b1fa2a7688a6795e3176330a3df3dadecce922e013ef86ff21fd0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4da3f29ec0ad99c14862e4a603023d02810b2a158ab1f55e6f0e581e0c9416a0 0.600000000000 1762925 of 15

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": 1275620, "vin": [ { "gen": { "height": 1275610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4da3f29ec0ad99c14862e4a603023d02810b2a158ab1f55e6f0e581e0c9416a0" } } ], "extra": [ 1, 131, 231, 174, 144, 219, 9, 177, 250, 42, 118, 136, 166, 121, 94, 49, 118, 51, 10, 61, 243, 218, 222, 204, 233, 34, 224, 19, 239, 134, 255, 33, 253, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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