Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5768164683727b7e3bcda3c2cf7803df9744ac385906faf0677f44246a96eda5

Tx prefix hash: c0c10e755cca5878052f15951fa2fb69717e7565ed17e7ee9f5f81198f630a24
Tx public key: deafb347e18016983c24263e46eae4bbc38ad63e588b11c1c99b3c1aa1d9320c
Timestamp: 1696585819 Timestamp [UCT]: 2023-10-06 09:50:19 Age [y:d:h:m:s]: 01:186:17:56:05
Block: 863641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394519 RingCT/type: yes/0
Extra: 01deafb347e18016983c24263e46eae4bbc38ad63e588b11c1c99b3c1aa1d9320c02110000000533af99f4000000000000000000

1 output(s) for total of 0.844119697000 dcy

stealth address amount amount idx
00: be105b458a2267ab4900d33a1e09780b711034d5d67a5c25e6d495c5b818e45b 0.844119697000 1318111 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": 863651, "vin": [ { "gen": { "height": 863641 } } ], "vout": [ { "amount": 844119697, "target": { "key": "be105b458a2267ab4900d33a1e09780b711034d5d67a5c25e6d495c5b818e45b" } } ], "extra": [ 1, 222, 175, 179, 71, 225, 128, 22, 152, 60, 36, 38, 62, 70, 234, 228, 187, 195, 138, 214, 62, 88, 139, 17, 193, 201, 155, 60, 26, 161, 217, 50, 12, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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