Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38278674bd0e010c26ac5521ef3052afbb05b3183533001b2aa2d13fd2eb5683

Tx prefix hash: d48a9cc460ca8de47e961352a82590a552715e1ef95338737e6ee6bcea656978
Tx public key: a9c1c5a46b03046b766a5f0cf9ec71fb0ad7d245e2469ad2e19581e22de5d92d
Timestamp: 1715916185 Timestamp [UCT]: 2024-05-17 03:23:05 Age [y:d:h:m:s]: 00:336:15:59:38
Block: 1023707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240645 RingCT/type: yes/0
Extra: 01a9c1c5a46b03046b766a5f0cf9ec71fb0ad7d245e2469ad2e19581e22de5d92d02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2496a60e973f33f01a8a38ae334fcd1e57a22d027b51ae3a578824a8bbcaa33 0.600000000000 1488878 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": 1023717, "vin": [ { "gen": { "height": 1023707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2496a60e973f33f01a8a38ae334fcd1e57a22d027b51ae3a578824a8bbcaa33" } } ], "extra": [ 1, 169, 193, 197, 164, 107, 3, 4, 107, 118, 106, 95, 12, 249, 236, 113, 251, 10, 215, 210, 69, 226, 70, 154, 210, 225, 149, 129, 226, 45, 229, 217, 45, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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