Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fdb051e2966a0baccffdeb558bdc577d9954f843fa4df3f8273777aa3eb61e7

Tx prefix hash: e332104aecc27492df511f88aaebe1792433c18a760dd5d2ae882cf32e8f38af
Tx public key: 99b34a5de859f0d69f3b8ac5e8d580ce97a339e5ea652e39f85a08d46797e3d5
Timestamp: 1733226029 Timestamp [UCT]: 2024-12-03 11:40:29 Age [y:d:h:m:s]: 00:110:19:52:44
Block: 1167104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78999 RingCT/type: yes/0
Extra: 0199b34a5de859f0d69f3b8ac5e8d580ce97a339e5ea652e39f85a08d46797e3d50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1649f8e3f5406ce07989f55d9cbc6817b5ae92436f79ba0171ec31753c40da0f 0.600000000000 1652797 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": 1167114, "vin": [ { "gen": { "height": 1167104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1649f8e3f5406ce07989f55d9cbc6817b5ae92436f79ba0171ec31753c40da0f" } } ], "extra": [ 1, 153, 179, 74, 93, 232, 89, 240, 214, 159, 59, 138, 197, 232, 213, 128, 206, 151, 163, 57, 229, 234, 101, 46, 57, 248, 90, 8, 212, 103, 151, 227, 213, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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