Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7e3d5a355d82898e174f9d4989172e93fc3ddc8d2e63f6f16d48a8e85d35947

Tx prefix hash: e0270756077bf3d54fc898d27ddf50d45776092aab513c8bcffb78985215c74d
Tx public key: 3629f000f33a412c88a9f5b1d8ea22728d33ef4040fa4d724df4e93dbed0be80
Timestamp: 1709433803 Timestamp [UCT]: 2024-03-03 02:43:23 Age [y:d:h:m:s]: 01:301:19:38:02
Block: 969965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474490 RingCT/type: yes/0
Extra: 013629f000f33a412c88a9f5b1d8ea22728d33ef4040fa4d724df4e93dbed0be8002110000000449a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1803b8483c215299b603d21cc47a22e1fe32ca1bf90d9a80f9cf193d21a10c45 0.600000000000 1429814 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": 969975, "vin": [ { "gen": { "height": 969965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1803b8483c215299b603d21cc47a22e1fe32ca1bf90d9a80f9cf193d21a10c45" } } ], "extra": [ 1, 54, 41, 240, 0, 243, 58, 65, 44, 136, 169, 245, 177, 216, 234, 34, 114, 141, 51, 239, 64, 64, 250, 77, 114, 77, 244, 233, 61, 190, 208, 190, 128, 2, 17, 0, 0, 0, 4, 73, 161, 133, 187, 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