Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a827dfe0fed7a417c60318b8e6c524f35b9f45a8aaee7d0fef14e7203caaa6a1

Tx prefix hash: 1924f6a9daf4965506ea1161b8c485961c3d78cc2e5aa1cfe987739debcc3a51
Tx public key: fc7d2bcfb187de3b03700632cbfeb29e6941c465a33cb7f0fac2a2c2b112c143
Timestamp: 1713026765 Timestamp [UCT]: 2024-04-13 16:46:05 Age [y:d:h:m:s]: 01:003:08:50:44
Block: 999722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263381 RingCT/type: yes/0
Extra: 01fc7d2bcfb187de3b03700632cbfeb29e6941c465a33cb7f0fac2a2c2b112c1430211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f689f3a272edd007a42e6c99e452a659aa00a91a5794042689085e91a2b09044 0.600000000000 1460204 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": 999732, "vin": [ { "gen": { "height": 999722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f689f3a272edd007a42e6c99e452a659aa00a91a5794042689085e91a2b09044" } } ], "extra": [ 1, 252, 125, 43, 207, 177, 135, 222, 59, 3, 112, 6, 50, 203, 254, 178, 158, 105, 65, 196, 101, 163, 60, 183, 240, 250, 194, 162, 194, 177, 18, 193, 67, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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