Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8f569ba3276e6642e827e48e71e3e54927115e705202882f423aaf3fa7c4ad0

Tx prefix hash: 0d6010b179430ddf1eb795d879ea2a0489b856e0d79a2516f2d1e9dfddcd1896
Tx public key: 674664ffc500e4d0a279589c7655fe3e23fc8a08d60daf2d851e15ed9a56a59e
Timestamp: 1734084467 Timestamp [UCT]: 2024-12-13 10:07:47 Age [y:d:h:m:s]: 00:105:00:39:58
Block: 1174236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74835 RingCT/type: yes/0
Extra: 01674664ffc500e4d0a279589c7655fe3e23fc8a08d60daf2d851e15ed9a56a59e021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51d93874c4da034d0dfdd17b268aeea31139d959bb1d170c2654ed84d268d536 0.600000000000 1660363 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": 1174246, "vin": [ { "gen": { "height": 1174236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51d93874c4da034d0dfdd17b268aeea31139d959bb1d170c2654ed84d268d536" } } ], "extra": [ 1, 103, 70, 100, 255, 197, 0, 228, 208, 162, 121, 88, 156, 118, 85, 254, 62, 35, 252, 138, 8, 214, 13, 175, 45, 133, 30, 21, 237, 154, 86, 165, 158, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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