Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e16521f7f54d3f5344f14310f9e4812c1ff01073e2e8791cba72a3f980716fc4

Tx prefix hash: 8964f8814ee4f439dcc83d29397a3c70cd4d37821ee6edac1a4f9ebbed17706c
Tx public key: 9efbec4119d3c7e5a37d573ead0855f23d04b3fd51fd7bbd44de091375b22d3f
Timestamp: 1718457704 Timestamp [UCT]: 2024-06-15 13:21:44 Age [y:d:h:m:s]: 00:343:22:59:34
Block: 1044779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245833 RingCT/type: yes/0
Extra: 019efbec4119d3c7e5a37d573ead0855f23d04b3fd51fd7bbd44de091375b22d3f0211000000038fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e15fa72dd94e75d1e450483042758717f3597e495ab5a752e24ad177c03b5a2a 0.600000000000 1514180 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": 1044789, "vin": [ { "gen": { "height": 1044779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e15fa72dd94e75d1e450483042758717f3597e495ab5a752e24ad177c03b5a2a" } } ], "extra": [ 1, 158, 251, 236, 65, 25, 211, 199, 229, 163, 125, 87, 62, 173, 8, 85, 242, 61, 4, 179, 253, 81, 253, 123, 189, 68, 222, 9, 19, 117, 178, 45, 63, 2, 17, 0, 0, 0, 3, 143, 218, 155, 45, 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