Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e3c8d75dcb96abf5a7948a83f665d0eb2b543061905747082a926902d865bf9

Tx prefix hash: a6772b41829fe2e5c8f291f707637fe77589942bbd0e0fd963ec3978984a9153
Tx public key: b458b43534da42ce663ccd236bded6f9f9d648e5a4b25b0e125f04650b454049
Timestamp: 1736562273 Timestamp [UCT]: 2025-01-11 02:24:33 Age [y:d:h:m:s]: 00:074:05:22:55
Block: 1194717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52816 RingCT/type: yes/0
Extra: 01b458b43534da42ce663ccd236bded6f9f9d648e5a4b25b0e125f04650b454049021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9fc80975938d5cf68186f5a05b7e57a9d69dfa322da2b3daa07762deafdd8f9 0.600000000000 1681294 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": 1194727, "vin": [ { "gen": { "height": 1194717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9fc80975938d5cf68186f5a05b7e57a9d69dfa322da2b3daa07762deafdd8f9" } } ], "extra": [ 1, 180, 88, 180, 53, 52, 218, 66, 206, 102, 60, 205, 35, 107, 222, 214, 249, 249, 214, 72, 229, 164, 178, 91, 14, 18, 95, 4, 101, 11, 69, 64, 73, 2, 17, 0, 0, 0, 2, 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