Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d77b0e2e1752922283399af83d493ef585d9eaee17881288c2c40a4d7380b691

Tx prefix hash: f7e5eca5da8ef32009a4572110feaffff94b958d322d2e177975d713ca8d1e92
Tx public key: 941eeda62609b6df5e46b122c7fde56efd494909e87511e674fc975c371f7e27
Timestamp: 1733462775 Timestamp [UCT]: 2024-12-06 05:26:15 Age [y:d:h:m:s]: 00:106:06:44:23
Block: 1169059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75762 RingCT/type: yes/0
Extra: 01941eeda62609b6df5e46b122c7fde56efd494909e87511e674fc975c371f7e270211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f2fdcea09a15695966c78c1f7ecae7e64e1c7dcdc9b0f1b557f8a64dcd5323f 0.600000000000 1654772 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": 1169069, "vin": [ { "gen": { "height": 1169059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f2fdcea09a15695966c78c1f7ecae7e64e1c7dcdc9b0f1b557f8a64dcd5323f" } } ], "extra": [ 1, 148, 30, 237, 166, 38, 9, 182, 223, 94, 70, 177, 34, 199, 253, 229, 110, 253, 73, 73, 9, 232, 117, 17, 230, 116, 252, 151, 92, 55, 31, 126, 39, 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