Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a69c7d1c59478aae5df5527bd8feab4db54d3e21295304568d18ff13458a03f

Tx prefix hash: 2b863225bd66cec1c16cd49d9b44f1de5630cceb47ec72a432390504d2fcf74e
Tx public key: 57a4c1dc4c72bcf1a85889d6f258e596b74024da13a5be5bd0910dc6535ab517
Timestamp: 1713802348 Timestamp [UCT]: 2024-04-22 16:12:28 Age [y:d:h:m:s]: 00:215:13:51:19
Block: 1006173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154318 RingCT/type: yes/0
Extra: 0157a4c1dc4c72bcf1a85889d6f258e596b74024da13a5be5bd0910dc6535ab51702110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f337d4c0874436f9addc6c940f1cdf111109fb4e41138332870fef4c378fb67f 0.600000000000 1467111 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": 1006183, "vin": [ { "gen": { "height": 1006173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f337d4c0874436f9addc6c940f1cdf111109fb4e41138332870fef4c378fb67f" } } ], "extra": [ 1, 87, 164, 193, 220, 76, 114, 188, 241, 168, 88, 137, 214, 242, 88, 229, 150, 183, 64, 36, 218, 19, 165, 190, 91, 208, 145, 13, 198, 83, 90, 181, 23, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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