Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f45f84283195d9be3ceed1cdb21fd460a46ca48f4eaa6b26459876ac713eb9b3

Tx prefix hash: 2dc76a44049a31c6b67991195c587f24f544fa56d6c0d1977bc1f3b42c135a55
Tx public key: b00e2ed7dda9172cb244f8cc3004f2f8398d9e89f2ceb3cd249ce223d2da6295
Timestamp: 1737276545 Timestamp [UCT]: 2025-01-19 08:49:05 Age [y:d:h:m:s]: 00:152:05:58:39
Block: 1200598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108517 RingCT/type: yes/0
Extra: 01b00e2ed7dda9172cb244f8cc3004f2f8398d9e89f2ceb3cd249ce223d2da6295021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efbb5330c5cef7993d81ec105d4d054ba888ac28de94a862abc847c1062aa935 0.600000000000 1687243 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": 1200608, "vin": [ { "gen": { "height": 1200598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efbb5330c5cef7993d81ec105d4d054ba888ac28de94a862abc847c1062aa935" } } ], "extra": [ 1, 176, 14, 46, 215, 221, 169, 23, 44, 178, 68, 248, 204, 48, 4, 242, 248, 57, 141, 158, 137, 242, 206, 179, 205, 36, 156, 226, 35, 210, 218, 98, 149, 2, 17, 0, 0, 0, 4, 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