Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baa01c076896c553d9d66f85392b2466981843a7ab51586542aa40a727eb61a7

Tx prefix hash: bceb6929a06a0e94571c8563602f5f859a4b692750bb6e284f909199e9e5d73b
Tx public key: cff4c950d29205c6fe45124c0a7f295750e4e8f6d0d69d16e77479b633b460f5
Timestamp: 1737535031 Timestamp [UCT]: 2025-01-22 08:37:11 Age [y:d:h:m:s]: 00:147:03:45:45
Block: 1202734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104921 RingCT/type: yes/0
Extra: 01cff4c950d29205c6fe45124c0a7f295750e4e8f6d0d69d16e77479b633b460f5021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64dc07c3d8f632ea0737e83193e122372bf1c2613d728d2e8b2ebde7958ea210 0.600000000000 1689399 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": 1202744, "vin": [ { "gen": { "height": 1202734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64dc07c3d8f632ea0737e83193e122372bf1c2613d728d2e8b2ebde7958ea210" } } ], "extra": [ 1, 207, 244, 201, 80, 210, 146, 5, 198, 254, 69, 18, 76, 10, 127, 41, 87, 80, 228, 232, 246, 208, 214, 157, 22, 231, 116, 121, 182, 51, 180, 96, 245, 2, 17, 0, 0, 0, 1, 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