Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09bc9eda540cfb53922fb5f512648bc6e8dfcc97d3d73ed4444f3c37f9893d27

Tx prefix hash: 5820129970b48140f5d8a7f79014a469ae42baaa4ee419689c8310b81991c4da
Tx public key: e23cfb64ae3cede4704a206373d93d156da1318cda4e15f836787a9d58f0d8d0
Timestamp: 1731328122 Timestamp [UCT]: 2024-11-11 12:28:42 Age [y:d:h:m:s]: 00:364:04:49:49
Block: 1151379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257842 RingCT/type: yes/0
Extra: 01e23cfb64ae3cede4704a206373d93d156da1318cda4e15f836787a9d58f0d8d002110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d57d3b20cb51c9e2fb24eb31ac254c9caf793f4581b1368e537bbf48a8814c 0.600000000000 1636900 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": 1151389, "vin": [ { "gen": { "height": 1151379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d57d3b20cb51c9e2fb24eb31ac254c9caf793f4581b1368e537bbf48a8814c" } } ], "extra": [ 1, 226, 60, 251, 100, 174, 60, 237, 228, 112, 74, 32, 99, 115, 217, 61, 21, 109, 161, 49, 140, 218, 78, 21, 248, 54, 120, 122, 157, 88, 240, 216, 208, 2, 17, 0, 0, 0, 13, 0, 127, 151, 138, 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