Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1096f2921331612bbd4e108dcff8afe14da4fd60b87c81daadb03d02ecfd3531

Tx prefix hash: cb4d34a540e05fc199eac7e77795c5697387cf29513b64db284b5c2241d2d788
Tx public key: 6d310c6f0d93a0ef254ad4fd9c6625aae005518e533c510a245efca54422949d
Timestamp: 1712473356 Timestamp [UCT]: 2024-04-07 07:02:36 Age [y:d:h:m:s]: 00:278:06:03:55
Block: 995123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199206 RingCT/type: yes/0
Extra: 016d310c6f0d93a0ef254ad4fd9c6625aae005518e533c510a245efca54422949d02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc65396546545847eb4eba3d23f5073ed55590833b8f25157b8e5ecaf64f67e9 0.600000000000 1455527 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": 995133, "vin": [ { "gen": { "height": 995123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc65396546545847eb4eba3d23f5073ed55590833b8f25157b8e5ecaf64f67e9" } } ], "extra": [ 1, 109, 49, 12, 111, 13, 147, 160, 239, 37, 74, 212, 253, 156, 102, 37, 170, 224, 5, 81, 142, 83, 60, 81, 10, 36, 94, 252, 165, 68, 34, 148, 157, 2, 17, 0, 0, 0, 1, 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