Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ec12743209800c493adbb383f6dad2bfb5982b14b2a5d304d5891bc9c3aa712

Tx prefix hash: 893c2068eb8917daabe57d6d9906a17c7d0a08ec250c908105b7e02a5ad171f8
Tx public key: e41ad1e47f8496fdebb6f9fa35c44474a4b4f82efa6f326b8bbbcb81f69f6d83
Timestamp: 1671995051 Timestamp [UCT]: 2022-12-25 19:04:11 Age [y:d:h:m:s]: 02:318:05:14:20
Block: 660453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 746833 RingCT/type: yes/0
Extra: 01e41ad1e47f8496fdebb6f9fa35c44474a4b4f82efa6f326b8bbbcb81f69f6d83021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.977818975000 dcy

stealth address amount amount idx
00: f4dc9a84e0e5c0b6ddf3b0f050e4e8cebb08513e06c76ef5ee357513ab125379 3.977818975000 1101186 of 0

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": 660463, "vin": [ { "gen": { "height": 660453 } } ], "vout": [ { "amount": 3977818975, "target": { "key": "f4dc9a84e0e5c0b6ddf3b0f050e4e8cebb08513e06c76ef5ee357513ab125379" } } ], "extra": [ 1, 228, 26, 209, 228, 127, 132, 150, 253, 235, 182, 249, 250, 53, 196, 68, 116, 164, 180, 248, 46, 250, 111, 50, 107, 139, 187, 203, 129, 246, 159, 109, 131, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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