Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7838932581f53789ff88f5e988c516d43a425c3c701a97ca6d828e3e92616a9

Tx prefix hash: 9494362ad26c23daa8125ddd95e25974802d1aa6fe4dc5343d1184a01a9bf075
Tx public key: bd13c642d9aa57a7ae71cbd3ac209e409a5d09311cce1f2b6c829a5b9a0db323
Timestamp: 1705767078 Timestamp [UCT]: 2024-01-20 16:11:18 Age [y:d:h:m:s]: 01:085:20:06:23
Block: 939528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322456 RingCT/type: yes/0
Extra: 01bd13c642d9aa57a7ae71cbd3ac209e409a5d09311cce1f2b6c829a5b9a0db3230211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1308efb6e43d159d9a4c214942d22009ea2a7610a47a3a10561389b8e90ff2b2 0.600000000000 1397636 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": 939538, "vin": [ { "gen": { "height": 939528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1308efb6e43d159d9a4c214942d22009ea2a7610a47a3a10561389b8e90ff2b2" } } ], "extra": [ 1, 189, 19, 198, 66, 217, 170, 87, 167, 174, 113, 203, 211, 172, 32, 158, 64, 154, 93, 9, 49, 28, 206, 31, 43, 108, 130, 154, 91, 154, 13, 179, 35, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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