Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f189cf141528bcaa55c9f49fb9cbb8141c98e379ac92093f6ec8ea7e2a6f76

Tx prefix hash: 476c45c7ee43733bc290b2f71f514af66c9f25f558d48de5433f0ea4571130b9
Tx public key: 2c8ad942a6b1fb04f347fd7fccc9abe5bac657613aa9926e9b976ba8a47871f7
Timestamp: 1723615240 Timestamp [UCT]: 2024-08-14 06:00:40 Age [y:d:h:m:s]: 00:230:03:20:59
Block: 1087527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164349 RingCT/type: yes/0
Extra: 012c8ad942a6b1fb04f347fd7fccc9abe5bac657613aa9926e9b976ba8a47871f702110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64fc9acfa3a1a05b8713c678eefaab94ae6d206e0978700e7c4952019b3dfa9c 0.600000000000 1562136 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": 1087537, "vin": [ { "gen": { "height": 1087527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64fc9acfa3a1a05b8713c678eefaab94ae6d206e0978700e7c4952019b3dfa9c" } } ], "extra": [ 1, 44, 138, 217, 66, 166, 177, 251, 4, 243, 71, 253, 127, 204, 201, 171, 229, 186, 198, 87, 97, 58, 169, 146, 110, 155, 151, 107, 168, 164, 120, 113, 247, 2, 17, 0, 0, 0, 12, 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