Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 885ec9f561b1b6f3aff6f6efdd6f086eae1fa816f41041f0c7e8d873be25cf23

Tx prefix hash: 7e7a35810b80f22ab8848721cabd54f116616f2c5da9010e1de0530705807d75
Tx public key: cf2b629793670c47e52d707e9dbdf370e4de1736851cc4e76be7ae101e7ee68d
Timestamp: 1764486531 Timestamp [UCT]: 2025-11-30 07:08:51 Age [y:d:h:m:s]: 00:022:17:46:55
Block: 1423241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16275 RingCT/type: yes/0
Extra: 01cf2b629793670c47e52d707e9dbdf370e4de1736851cc4e76be7ae101e7ee68d021100000002defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fa23d572b8e400b5f073770a54033415b3c881b8328d6cbd6d7428088a5ad93 0.600000000000 1911844 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": 1423251, "vin": [ { "gen": { "height": 1423241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fa23d572b8e400b5f073770a54033415b3c881b8328d6cbd6d7428088a5ad93" } } ], "extra": [ 1, 207, 43, 98, 151, 147, 103, 12, 71, 229, 45, 112, 126, 157, 189, 243, 112, 228, 222, 23, 54, 133, 28, 196, 231, 107, 231, 174, 16, 30, 126, 230, 141, 2, 17, 0, 0, 0, 2, 222, 251, 143, 24, 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