Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e336233f017f6da09536c7839eb9cbce972cb0871dfdd58d48d02aa43bafac4

Tx prefix hash: 2b8dafe934589a585ee219089b2efc43dc72f7119aeb1637f40d182034297aa6
Tx public key: 478c364a1b7ade40ade10d18654c004804d94741f5d564aa8aa36f5aa2fb4c7e
Timestamp: 1736805916 Timestamp [UCT]: 2025-01-13 22:05:16 Age [y:d:h:m:s]: 00:312:00:49:50
Block: 1196739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220520 RingCT/type: yes/0
Extra: 01478c364a1b7ade40ade10d18654c004804d94741f5d564aa8aa36f5aa2fb4c7e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7d053ebaf1e493fdfcc5b632961c241d1b0f0211cb698c8020db8fc3cd0df91 0.600000000000 1683342 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": 1196749, "vin": [ { "gen": { "height": 1196739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7d053ebaf1e493fdfcc5b632961c241d1b0f0211cb698c8020db8fc3cd0df91" } } ], "extra": [ 1, 71, 140, 54, 74, 27, 122, 222, 64, 173, 225, 13, 24, 101, 76, 0, 72, 4, 217, 71, 65, 245, 213, 100, 170, 138, 163, 111, 90, 162, 251, 76, 126, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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