Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c7cc1b2f50fa4cae699492df838e367ede7bed95d8589a6c5fd88254601a80f

Tx prefix hash: 3f8860a1354239403ec7f3feaf85913087dc0b53c3e9cc4cc562f0b2c50cc6d1
Tx public key: 2ed1a551acfab76da2d648b625a6392075fca7e48d0650af6b8e05ae648a0211
Timestamp: 1760507187 Timestamp [UCT]: 2025-10-15 05:46:27 Age [y:d:h:m:s]: 00:024:05:35:57
Block: 1390272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17336 RingCT/type: yes/0
Extra: 012ed1a551acfab76da2d648b625a6392075fca7e48d0650af6b8e05ae648a02110211000000072609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32e3fcfd8f254ae3ce71dd4eb85a08915cad82d7cfe6115a5c2ab09eb3f90bdf 0.600000000000 1878509 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": 1390282, "vin": [ { "gen": { "height": 1390272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32e3fcfd8f254ae3ce71dd4eb85a08915cad82d7cfe6115a5c2ab09eb3f90bdf" } } ], "extra": [ 1, 46, 209, 165, 81, 172, 250, 183, 109, 162, 214, 72, 182, 37, 166, 57, 32, 117, 252, 167, 228, 141, 6, 80, 175, 107, 142, 5, 174, 100, 138, 2, 17, 2, 17, 0, 0, 0, 7, 38, 9, 179, 160, 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