Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f77c9bacaf0aced6ba3cdb46014d0e56b14d9848cd2c4b127f4f146d0830d7db

Tx prefix hash: fb811f90171854a628f7f6d5c1699de13f88e77085b28c1559ef0071c06cc4e8
Tx public key: fd1e2d291110ae2e5aa7ca27ff577964224e0d994a424fd88aba4dd83971b10b
Timestamp: 1720101347 Timestamp [UCT]: 2024-07-04 13:55:47 Age [y:d:h:m:s]: 00:191:04:54:09
Block: 1058388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136824 RingCT/type: yes/0
Extra: 01fd1e2d291110ae2e5aa7ca27ff577964224e0d994a424fd88aba4dd83971b10b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8224998581deb469e8888db2737ec17c1e0ad0581b35dce706b8fad3ab96351 0.600000000000 1528843 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": 1058398, "vin": [ { "gen": { "height": 1058388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8224998581deb469e8888db2737ec17c1e0ad0581b35dce706b8fad3ab96351" } } ], "extra": [ 1, 253, 30, 45, 41, 17, 16, 174, 46, 90, 167, 202, 39, 255, 87, 121, 100, 34, 78, 13, 153, 74, 66, 79, 216, 138, 186, 77, 216, 57, 113, 177, 11, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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