Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9272e4f1b2c7c285a31f7eeb6667a2b5c36c76aa10a5922658fd2fd653b5efa

Tx prefix hash: 3cc4d04a10e599520a9c4be8afadff7178118c19a4a40f4b7d3630ca61c8fa99
Tx public key: 13784700340d748e42852dcd2f53c9a7baee344dc765f5a83df353e11c316ad3
Timestamp: 1765921863 Timestamp [UCT]: 2025-12-16 21:51:03 Age [y:d:h:m:s]: 00:017:12:31:02
Block: 1435133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12559 RingCT/type: yes/0
Extra: 0113784700340d748e42852dcd2f53c9a7baee344dc765f5a83df353e11c316ad30211000000057b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3740a49205f7cbebcf9617011a62339b3d2e9e31126f1cf65a58ba57c0314e1 0.600000000000 1923930 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": 1435143, "vin": [ { "gen": { "height": 1435133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3740a49205f7cbebcf9617011a62339b3d2e9e31126f1cf65a58ba57c0314e1" } } ], "extra": [ 1, 19, 120, 71, 0, 52, 13, 116, 142, 66, 133, 45, 205, 47, 83, 201, 167, 186, 238, 52, 77, 199, 101, 245, 168, 61, 243, 83, 225, 28, 49, 106, 211, 2, 17, 0, 0, 0, 5, 123, 30, 81, 172, 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