Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a10d7048c4e9a7bf0487422f793e7a31206af9589b30b645052b5993f5463ba9

Tx prefix hash: 0d2faf877ad2f811199dfeb78446edd999ff4690fe697388d8d6fa5f09b66c5e
Tx public key: 78cae164a82cf843f068b26748616c6a11a0c272da09bb110dfb6f390b3cb38c
Timestamp: 1648489761 Timestamp [UCT]: 2022-03-28 17:49:21 Age [y:d:h:m:s]: 03:081:10:34:20
Block: 468358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 838345 RingCT/type: yes/0
Extra: 0178cae164a82cf843f068b26748616c6a11a0c272da09bb110dfb6f390b3cb38c021100000006cb8520c2000000000000000000

1 output(s) for total of 17.224069659000 dcy

stealth address amount amount idx
00: 0679ee526bb8494fac01fa66b11f7c1135ded520f2097d5d0f32da9890ae7f91 17.224069659000 887062 of 0

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": 468368, "vin": [ { "gen": { "height": 468358 } } ], "vout": [ { "amount": 17224069659, "target": { "key": "0679ee526bb8494fac01fa66b11f7c1135ded520f2097d5d0f32da9890ae7f91" } } ], "extra": [ 1, 120, 202, 225, 100, 168, 44, 248, 67, 240, 104, 178, 103, 72, 97, 108, 106, 17, 160, 194, 114, 218, 9, 187, 17, 13, 251, 111, 57, 11, 60, 179, 140, 2, 17, 0, 0, 0, 6, 203, 133, 32, 194, 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