Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccdb1791dc3df43ca269186fbceaeda15a96ea5cdd50fe0ccb4569d203af6974

Tx prefix hash: 1ad7c8fbba131d46791421b78766b38cb47d5da9a3f5593e604ea92831e78175
Tx public key: 0eac3d1cda6ed4d41c19d24331b9a485aebe0428c60db8cc44dd4e49e57afec5
Timestamp: 1736901662 Timestamp [UCT]: 2025-01-15 00:41:02 Age [y:d:h:m:s]: 00:059:08:40:38
Block: 1197531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42216 RingCT/type: yes/0
Extra: 010eac3d1cda6ed4d41c19d24331b9a485aebe0428c60db8cc44dd4e49e57afec5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 889312284a15fd45bf0e7dbf502780b64a0715c47c29f11346ed4da9d1e48e90 0.600000000000 1684142 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": 1197541, "vin": [ { "gen": { "height": 1197531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "889312284a15fd45bf0e7dbf502780b64a0715c47c29f11346ed4da9d1e48e90" } } ], "extra": [ 1, 14, 172, 61, 28, 218, 110, 212, 212, 28, 25, 210, 67, 49, 185, 164, 133, 174, 190, 4, 40, 198, 13, 184, 204, 68, 221, 78, 73, 229, 122, 254, 197, 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