Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf8cf7196ebf90734086882f6c8c51e1dc16ce78fb484c2b67cb83fa6f33e8b

Tx prefix hash: 093fe434cc8f1f1b5ddf21460593ebc8a0a2faeee9923298d02975ff9e25d30a
Tx public key: cc170a69f14b5ca5cc089eabdac7fde1bf974ed29377f58563a5260648e6545b
Timestamp: 1712879938 Timestamp [UCT]: 2024-04-11 23:58:58 Age [y:d:h:m:s]: 01:031:06:31:41
Block: 998501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283334 RingCT/type: yes/0
Extra: 01cc170a69f14b5ca5cc089eabdac7fde1bf974ed29377f58563a5260648e6545b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df44f6da400e1a3229bacb14563500e4dbbf4ccde089d31e8dc72ab4f544f6dd 0.600000000000 1458953 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": 998511, "vin": [ { "gen": { "height": 998501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df44f6da400e1a3229bacb14563500e4dbbf4ccde089d31e8dc72ab4f544f6dd" } } ], "extra": [ 1, 204, 23, 10, 105, 241, 75, 92, 165, 204, 8, 158, 171, 218, 199, 253, 225, 191, 151, 78, 210, 147, 119, 245, 133, 99, 165, 38, 6, 72, 230, 84, 91, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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