Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25e353427b0a2ab2dd385f49b631a872a2e5ab7ab170bd0e0f991ee5191ff117

Tx prefix hash: 31cfa8b7019241e19b0b9762489312307024856d056d9c42a0c4460a3d91c5ab
Tx public key: 8f2a06ae7991a85d8e1ad1e46f84536c660f203f2abb48013a68f437389f7402
Timestamp: 1728862293 Timestamp [UCT]: 2024-10-13 23:31:33 Age [y:d:h:m:s]: 00:251:01:53:37
Block: 1131026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179098 RingCT/type: yes/0
Extra: 018f2a06ae7991a85d8e1ad1e46f84536c660f203f2abb48013a68f437389f7402021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0eeb223cb6ca83ad74a97ba2c729f71fb436e7c6f8e7147eb6ea2a2f01a76568 0.600000000000 1613907 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": 1131036, "vin": [ { "gen": { "height": 1131026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eeb223cb6ca83ad74a97ba2c729f71fb436e7c6f8e7147eb6ea2a2f01a76568" } } ], "extra": [ 1, 143, 42, 6, 174, 121, 145, 168, 93, 142, 26, 209, 228, 111, 132, 83, 108, 102, 15, 32, 63, 42, 187, 72, 1, 58, 104, 244, 55, 56, 159, 116, 2, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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