Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80da0de1793301b4b60d3d0ecdec5c47e4a673a5071cd9d8fb6c9e3319a392dc

Tx prefix hash: 93136655fd05e6ef8fe65cf792555fcd6ca1446ad41a36c2601a4f60c8285503
Tx public key: 48347b519a7c62f126c5d5e9008c021d9a4b2de9566910e37d86b03c920481c2
Timestamp: 1702305874 Timestamp [UCT]: 2023-12-11 14:44:34 Age [y:d:h:m:s]: 01:040:13:08:53
Block: 910860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290305 RingCT/type: yes/0
Extra: 0148347b519a7c62f126c5d5e9008c021d9a4b2de9566910e37d86b03c920481c202110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d50bf22d09f670e724e43d16a582eb80668453aa3f6a21e48bb7604c154b29e8 0.600000000000 1368035 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": 910870, "vin": [ { "gen": { "height": 910860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d50bf22d09f670e724e43d16a582eb80668453aa3f6a21e48bb7604c154b29e8" } } ], "extra": [ 1, 72, 52, 123, 81, 154, 124, 98, 241, 38, 197, 213, 233, 0, 140, 2, 29, 154, 75, 45, 233, 86, 105, 16, 227, 125, 134, 176, 60, 146, 4, 129, 194, 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