Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d1b54fc897eaa837082b68e6100267121363d23630a9209e925aabe080c2c16

Tx prefix hash: 56564069b9274df6d28a4dd362fbec1f5c5c10c67ad5a1c5d8f900e7c1b23e1d
Tx public key: ea1de56c7c4509cb38bc4aa3d93e39f485c524ec71e02d5e240f4f8e92b78141
Timestamp: 1622796178 Timestamp [UCT]: 2021-06-04 08:42:58 Age [y:d:h:m:s]: 03:315:09:21:27
Block: 271944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 989507 RingCT/type: yes/0
Extra: 01ea1de56c7c4509cb38bc4aa3d93e39f485c524ec71e02d5e240f4f8e92b7814102110000000623fdb90b000000000000000000

1 output(s) for total of 77.079194867000 dcy

stealth address amount amount idx
00: fe189783164e034b8f38adbcf8806c30e18ec46588a0522c59d2184ebd7d6cc0 77.079194867000 570768 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": 271954, "vin": [ { "gen": { "height": 271944 } } ], "vout": [ { "amount": 77079194867, "target": { "key": "fe189783164e034b8f38adbcf8806c30e18ec46588a0522c59d2184ebd7d6cc0" } } ], "extra": [ 1, 234, 29, 229, 108, 124, 69, 9, 203, 56, 188, 74, 163, 217, 62, 57, 244, 133, 197, 36, 236, 113, 224, 45, 94, 36, 15, 79, 142, 146, 183, 129, 65, 2, 17, 0, 0, 0, 6, 35, 253, 185, 11, 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