Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 724813cc8abbd0f74cc96054e7a9665f712bde41fb49436a75d33127590625c5

Tx prefix hash: 7f8492819c9f4b6d68d729f44e57b83f8d1bc70c191f70bbe6cdfde2140c2b35
Tx public key: cdc95a37a23ef6bcb640aa2ab1b8e36b3adb8a2ed11d72cebb747902d21cc3bb
Timestamp: 1746530967 Timestamp [UCT]: 2025-05-06 11:29:27 Age [y:d:h:m:s]: 00:268:16:19:14
Block: 1276976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189663 RingCT/type: yes/0
Extra: 01cdc95a37a23ef6bcb640aa2ab1b8e36b3adb8a2ed11d72cebb747902d21cc3bb0211000000051f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d48e26848fe0fd6c55fe28dc9e96a7925ee50bc85e83afbdfc1d17fc44ed15e6 0.600000000000 1764327 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": 1276986, "vin": [ { "gen": { "height": 1276976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d48e26848fe0fd6c55fe28dc9e96a7925ee50bc85e83afbdfc1d17fc44ed15e6" } } ], "extra": [ 1, 205, 201, 90, 55, 162, 62, 246, 188, 182, 64, 170, 42, 177, 184, 227, 107, 58, 219, 138, 46, 209, 29, 114, 206, 187, 116, 121, 2, 210, 28, 195, 187, 2, 17, 0, 0, 0, 5, 31, 144, 81, 122, 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