Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 445ee42af27c5df90117f72b8a824892854b9841752c85f04650e5c96838e7e9

Tx prefix hash: 4d57dc88b2dee7bd15a9ac96d819f2d304a0087fea84e1d5c76d50284bd166f9
Tx public key: 537ce34760cace01c1f8475d624bb520a9004fe4aa1b5ed11907cbbb59a596fe
Timestamp: 1669127790 Timestamp [UCT]: 2022-11-22 14:36:30 Age [y:d:h:m:s]: 02:147:15:34:03
Block: 636696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 627256 RingCT/type: yes/0
Extra: 01537ce34760cace01c1f8475d624bb520a9004fe4aa1b5ed11907cbbb59a596fe02110000000483600029000000000000000000

1 output(s) for total of 4.768281132000 dcy

stealth address amount amount idx
00: 35d8d964719f4888e2c4288a53b48b8b980da20e7b2d58fc0b50323bd7a22e2d 4.768281132000 1076160 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": 636706, "vin": [ { "gen": { "height": 636696 } } ], "vout": [ { "amount": 4768281132, "target": { "key": "35d8d964719f4888e2c4288a53b48b8b980da20e7b2d58fc0b50323bd7a22e2d" } } ], "extra": [ 1, 83, 124, 227, 71, 96, 202, 206, 1, 193, 248, 71, 93, 98, 75, 181, 32, 169, 0, 79, 228, 170, 27, 94, 209, 25, 7, 203, 187, 89, 165, 150, 254, 2, 17, 0, 0, 0, 4, 131, 96, 0, 41, 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