Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0c26459f70c1b743f06b5f9ac13f6860599d2b28c2e5ec2617d5b0972d8a378

Tx prefix hash: 0ce3d575010430e142a3fe21e23896d6af8e799798415a9f1c1bc0f237892087
Tx public key: 1f9dbd1c78f11f2ddc7cc98f4e1c10f5fe52ef9290593815ad612debace98b02
Timestamp: 1730787106 Timestamp [UCT]: 2024-11-05 06:11:46 Age [y:d:h:m:s]: 01:031:06:48:14
Block: 1146894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280813 RingCT/type: yes/0
Extra: 011f9dbd1c78f11f2ddc7cc98f4e1c10f5fe52ef9290593815ad612debace98b02021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6171905271ebf398e5899ec1c80abfc01985209cfe578f4fc4a8cdb1048702f3 0.600000000000 1631585 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": 1146904, "vin": [ { "gen": { "height": 1146894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6171905271ebf398e5899ec1c80abfc01985209cfe578f4fc4a8cdb1048702f3" } } ], "extra": [ 1, 31, 157, 189, 28, 120, 241, 31, 45, 220, 124, 201, 143, 78, 28, 16, 245, 254, 82, 239, 146, 144, 89, 56, 21, 173, 97, 45, 235, 172, 233, 139, 2, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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