Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d0c40d7a0b21a642fef52aa6a7e1294522c5e1d2440a3e1ed339688cf030178

Tx prefix hash: c0d2579581f2fc35ce1958d3ef97e175556bdc131a1f3b0f3be7fe5d1b8c39a2
Tx public key: 707ea78c71be106f930a530d1ff03e33737c2e35e336ea7fe3dcad2646ecb657
Timestamp: 1727491512 Timestamp [UCT]: 2024-09-28 02:45:12 Age [y:d:h:m:s]: 00:116:16:36:18
Block: 1119665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83388 RingCT/type: yes/0
Extra: 01707ea78c71be106f930a530d1ff03e33737c2e35e336ea7fe3dcad2646ecb65702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aba4dba61a575113543ea0de2fcd18baa011027632ef69b77b14e5cb5e1c4cc6 0.600000000000 1601304 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": 1119675, "vin": [ { "gen": { "height": 1119665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aba4dba61a575113543ea0de2fcd18baa011027632ef69b77b14e5cb5e1c4cc6" } } ], "extra": [ 1, 112, 126, 167, 140, 113, 190, 16, 111, 147, 10, 83, 13, 31, 240, 62, 51, 115, 124, 46, 53, 227, 54, 234, 127, 227, 220, 173, 38, 70, 236, 182, 87, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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