Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 800c98886f272bfd8eb3b5282bae9458e89ef8a312cf265e0725ac425fec573e

Tx prefix hash: 48e9e8bfae67baf47b1fba51fc80cfce52e7ce6830941522f38bf064ee0f34fb
Tx public key: f5869ddaec1f178a9c2e6e31e1d0ca3d33c7621c60185e8a3785d0b0d81c492b
Timestamp: 1702679360 Timestamp [UCT]: 2023-12-15 22:29:20 Age [y:d:h:m:s]: 01:035:15:28:11
Block: 913954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286796 RingCT/type: yes/0
Extra: 01f5869ddaec1f178a9c2e6e31e1d0ca3d33c7621c60185e8a3785d0b0d81c492b02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4034257a03be6ce51a4dbf7344012df88c361714b28f3e35fc83486362ae947 0.600000000000 1371234 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": 913964, "vin": [ { "gen": { "height": 913954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4034257a03be6ce51a4dbf7344012df88c361714b28f3e35fc83486362ae947" } } ], "extra": [ 1, 245, 134, 157, 218, 236, 31, 23, 138, 156, 46, 110, 49, 225, 208, 202, 61, 51, 199, 98, 28, 96, 24, 94, 138, 55, 133, 208, 176, 216, 28, 73, 43, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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