Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a70cbd17354231c55b1013a8bf0a2f71caca0f044355d02c44b4d7e0ff8155c6

Tx prefix hash: e1a88717ed2e7bb6cfd4032580eb025b5e8a9d49250c561de494b4b4748254a9
Tx public key: 1e2091953f8c1794894e9f938a67f60ffda2fab819c00c8ca3f55c1d8436162b
Timestamp: 1732903739 Timestamp [UCT]: 2024-11-29 18:08:59 Age [y:d:h:m:s]: 00:112:13:45:28
Block: 1164439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80254 RingCT/type: yes/0
Extra: 011e2091953f8c1794894e9f938a67f60ffda2fab819c00c8ca3f55c1d8436162b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5d34d4a946d682a8d772335b480da131baa177886ed15698440ec78df9fa4fb 0.600000000000 1650112 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": 1164449, "vin": [ { "gen": { "height": 1164439 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5d34d4a946d682a8d772335b480da131baa177886ed15698440ec78df9fa4fb" } } ], "extra": [ 1, 30, 32, 145, 149, 63, 140, 23, 148, 137, 78, 159, 147, 138, 103, 246, 15, 253, 162, 250, 184, 25, 192, 12, 140, 163, 245, 92, 29, 132, 54, 22, 43, 2, 17, 0, 0, 0, 3, 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