Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5c327cd8335ae8e10b8002ab3cf3bce96fa8eb03670e54e32aa60f476eb10d0

Tx prefix hash: 440dfb97c902a60afad788ed61d45fee959a0603d85a6944e4b3d2461ef82830
Tx public key: 8aec1834005e50f27d52f8f4ecbc634675482cac47fe64ea801bcf3bdc870312
Timestamp: 1763968830 Timestamp [UCT]: 2025-11-24 07:20:30 Age [y:d:h:m:s]: 00:064:05:46:38
Block: 1418944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45816 RingCT/type: yes/0
Extra: 018aec1834005e50f27d52f8f4ecbc634675482cac47fe64ea801bcf3bdc870312021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2181ab78d4f9f713d18d8dcedbfc8fba1bc92c94c0b8a508f06d42449197fb6b 0.600000000000 1907477 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": 1418954, "vin": [ { "gen": { "height": 1418944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2181ab78d4f9f713d18d8dcedbfc8fba1bc92c94c0b8a508f06d42449197fb6b" } } ], "extra": [ 1, 138, 236, 24, 52, 0, 94, 80, 242, 125, 82, 248, 244, 236, 188, 99, 70, 117, 72, 44, 172, 71, 254, 100, 234, 128, 27, 207, 59, 220, 135, 3, 18, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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