Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc83caea3e6238f31ea3969f30b0bc5247b8793f5b6f5c1a4159bbbf6d580902

Tx prefix hash: 4928a9f6d51e6fb3b7970b010a4784d21447f49045a7be3c1ba872ef074f5d81
Tx public key: 96f865178ae1eb8e4a6810827c2ecc1da94166f2f5a0b1d33445e48ca87ae54e
Timestamp: 1749952947 Timestamp [UCT]: 2025-06-15 02:02:27 Age [y:d:h:m:s]: 00:159:22:29:43
Block: 1305221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112087 RingCT/type: yes/0
Extra: 0196f865178ae1eb8e4a6810827c2ecc1da94166f2f5a0b1d33445e48ca87ae54e021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0ccc37d7d8507a3e69c56d8db80bcd460925e81ed06dc38ba66923268a2e9e1 0.600000000000 1792820 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": 1305231, "vin": [ { "gen": { "height": 1305221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0ccc37d7d8507a3e69c56d8db80bcd460925e81ed06dc38ba66923268a2e9e1" } } ], "extra": [ 1, 150, 248, 101, 23, 138, 225, 235, 142, 74, 104, 16, 130, 124, 46, 204, 29, 169, 65, 102, 242, 245, 160, 177, 211, 52, 69, 228, 140, 168, 122, 229, 78, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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