Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a1e89b63bf20e6a99d9a9d3c1e64a923a14fe5ca577c44e08f4868c29a98f4c

Tx prefix hash: 83427518874dd2d0bf0f50653ad3133c14d25be9c58171c378529791321a428d
Tx public key: 1ea9d5551dacae444334f309f1d573e09f40fe4a62426ec834d3e7f91e0b35b4
Timestamp: 1734772001 Timestamp [UCT]: 2024-12-21 09:06:41 Age [y:d:h:m:s]: 00:177:14:10:01
Block: 1179932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126623 RingCT/type: yes/0
Extra: 011ea9d5551dacae444334f309f1d573e09f40fe4a62426ec834d3e7f91e0b35b4021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c49aca177fc2534df3cf6b6e39b46aa4ce81303628c596328637ccfd453d902 0.600000000000 1666333 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": 1179942, "vin": [ { "gen": { "height": 1179932 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c49aca177fc2534df3cf6b6e39b46aa4ce81303628c596328637ccfd453d902" } } ], "extra": [ 1, 30, 169, 213, 85, 29, 172, 174, 68, 67, 52, 243, 9, 241, 213, 115, 224, 159, 64, 254, 74, 98, 66, 110, 200, 52, 211, 231, 249, 30, 11, 53, 180, 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