Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26a09a23e0508c22b845eb193f927d90836ca09194c8979fec4eb6375f19fb75

Tx prefix hash: 8582948cf2d654bc503b08e8a52af0427058262d06fbc6d239a3e072cb63724e
Tx public key: 2328df6f45b027ae2eb8e0a3bc6bb6d05ceaa314a9c8f6669d49321755339661
Timestamp: 1726980186 Timestamp [UCT]: 2024-09-22 04:43:06 Age [y:d:h:m:s]: 00:064:00:39:25
Block: 1115419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45763 RingCT/type: yes/0
Extra: 012328df6f45b027ae2eb8e0a3bc6bb6d05ceaa314a9c8f6669d4932175533966102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7b7777933027249e0f1fb18a3a924e203ffb332c365bedd7966970b2b543ed 0.600000000000 1595546 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": 1115429, "vin": [ { "gen": { "height": 1115419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7b7777933027249e0f1fb18a3a924e203ffb332c365bedd7966970b2b543ed" } } ], "extra": [ 1, 35, 40, 223, 111, 69, 176, 39, 174, 46, 184, 224, 163, 188, 107, 182, 208, 92, 234, 163, 20, 169, 200, 246, 102, 157, 73, 50, 23, 85, 51, 150, 97, 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