Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66b9549ee5a3d38cc0b32729c1690ff9a58ab1ddf67a0c16df485abcc8799524

Tx prefix hash: f329974e16233e6e06d23ebbdf4d6076789592eef9cfe16f58508dde97914435
Tx public key: f69749dc06fd6ab5e3b1c4e7c2a4da778f2251b35dd34f3f4edf3d957d8a828d
Timestamp: 1719888533 Timestamp [UCT]: 2024-07-02 02:48:53 Age [y:d:h:m:s]: 00:329:16:28:25
Block: 1056627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235616 RingCT/type: yes/0
Extra: 01f69749dc06fd6ab5e3b1c4e7c2a4da778f2251b35dd34f3f4edf3d957d8a828d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee59cb84a10c12e06c64055314bd836ab9342ff401be76ed5185cb695e8eb61b 0.600000000000 1527044 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": 1056637, "vin": [ { "gen": { "height": 1056627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee59cb84a10c12e06c64055314bd836ab9342ff401be76ed5185cb695e8eb61b" } } ], "extra": [ 1, 246, 151, 73, 220, 6, 253, 106, 181, 227, 177, 196, 231, 194, 164, 218, 119, 143, 34, 81, 179, 93, 211, 79, 63, 78, 223, 61, 149, 125, 138, 130, 141, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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