Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce25763ab50b912adada43d99b8e0d3ca4a6dc2b32e621e8a7ccfb99e988712

Tx prefix hash: ba265466e0356e856963b034cb950238ec00394ff6086e6f2c1989da41f8cfdf
Tx public key: d6405bd289a0d1ea16d133921be1233186d93d1e8b22603a9d4aa831eea64ec5
Timestamp: 1745853032 Timestamp [UCT]: 2025-04-28 15:10:32 Age [y:d:h:m:s]: 00:014:03:12:18
Block: 1271380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10099 RingCT/type: yes/0
Extra: 01d6405bd289a0d1ea16d133921be1233186d93d1e8b22603a9d4aa831eea64ec50211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11696f10abb220f4fc697ce66bd1ee18a31118c0af5c35fde0d55b8e566de0d5 0.600000000000 1758641 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": 1271390, "vin": [ { "gen": { "height": 1271380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11696f10abb220f4fc697ce66bd1ee18a31118c0af5c35fde0d55b8e566de0d5" } } ], "extra": [ 1, 214, 64, 91, 210, 137, 160, 209, 234, 22, 209, 51, 146, 27, 225, 35, 49, 134, 217, 61, 30, 139, 34, 96, 58, 157, 74, 168, 49, 238, 166, 78, 197, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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