Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4bbc527b6ec3e36cd92b6ba714c59fbcd52e2c4e0691a474851829b56602db

Tx prefix hash: 8baf90bd349f068601ea9c80a050ab71844cc69c6f85ab3aeedcd918eb91203c
Tx public key: 785f551e6fd1d39e795e2a404226d7bba573ba5b61f83ac0f8218ca6fce234a9
Timestamp: 1741450822 Timestamp [UCT]: 2025-03-08 16:20:22 Age [y:d:h:m:s]: 00:323:16:15:27
Block: 1234935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228976 RingCT/type: yes/0
Extra: 01785f551e6fd1d39e795e2a404226d7bba573ba5b61f83ac0f8218ca6fce234a90211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35e4d729d8c6647009fb2981a8460e8b86bbe49af20311b44c1eaa5e6a528b3d 0.600000000000 1721870 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": 1234945, "vin": [ { "gen": { "height": 1234935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35e4d729d8c6647009fb2981a8460e8b86bbe49af20311b44c1eaa5e6a528b3d" } } ], "extra": [ 1, 120, 95, 85, 30, 111, 209, 211, 158, 121, 94, 42, 64, 66, 38, 215, 187, 165, 115, 186, 91, 97, 248, 58, 192, 248, 33, 140, 166, 252, 226, 52, 169, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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