Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f26e9bb5449d537e34da5674f72fd5edd93237bb2934b8b16539f33efbe11b00

Tx prefix hash: a0460dd2d1938ba358ccbe6a63aa040bdf2ca0897d931522ff315cc3b9f8412b
Tx public key: 0f646c68dc0957f5fb1608bc6ff1759b7e9bebb34734f97a900f9fa994eadf0b
Timestamp: 1737605118 Timestamp [UCT]: 2025-01-23 04:05:18 Age [y:d:h:m:s]: 00:145:12:23:45
Block: 1203316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103748 RingCT/type: yes/0
Extra: 010f646c68dc0957f5fb1608bc6ff1759b7e9bebb34734f97a900f9fa994eadf0b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e1ad0071dc59d01c4d75048fe5a420da1e138e0880ab2a82bf53be4b9e4d76b 0.600000000000 1689991 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": 1203326, "vin": [ { "gen": { "height": 1203316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e1ad0071dc59d01c4d75048fe5a420da1e138e0880ab2a82bf53be4b9e4d76b" } } ], "extra": [ 1, 15, 100, 108, 104, 220, 9, 87, 245, 251, 22, 8, 188, 111, 241, 117, 155, 126, 155, 235, 179, 71, 52, 249, 122, 144, 15, 159, 169, 148, 234, 223, 11, 2, 17, 0, 0, 0, 5, 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