Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d54e16cd6a451a061276a016f99921ed10c0c4f44f076050da1bd5a4a585b9

Tx prefix hash: 40a72b6c948d07687d81c3a1a8904756348a619b7f0b7ce688b0e563e44e9ae3
Tx public key: bd8baf940df8707d7ed1783b721517a3b09b5cd93d2ad3959c21bf3b4a797e03
Timestamp: 1738233638 Timestamp [UCT]: 2025-01-30 10:40:38 Age [y:d:h:m:s]: 00:137:19:21:38
Block: 1208303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98454 RingCT/type: yes/0
Extra: 01bd8baf940df8707d7ed1783b721517a3b09b5cd93d2ad3959c21bf3b4a797e03021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbf43e3c902c60abf63a4d337abd9f0b1ce0b4af4a8502fe902ae51ab0f3ddfd 0.600000000000 1695034 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": 1208313, "vin": [ { "gen": { "height": 1208303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbf43e3c902c60abf63a4d337abd9f0b1ce0b4af4a8502fe902ae51ab0f3ddfd" } } ], "extra": [ 1, 189, 139, 175, 148, 13, 248, 112, 125, 126, 209, 120, 59, 114, 21, 23, 163, 176, 155, 92, 217, 61, 42, 211, 149, 156, 33, 191, 59, 74, 121, 126, 3, 2, 17, 0, 0, 0, 5, 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