Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f539043f4e07e710be1340a96916ff43a58a27dd0e414c7921c426f5b77275b

Tx prefix hash: 7e59521defc1103f1c93301810c6ab44eb10eeadac8efa5cbe4dc4f9e7263993
Tx public key: 8e45abbaa727ab99edaa40fca0f8dc5a25fe0fb94bf7fde1cf393f2990b31648
Timestamp: 1702227828 Timestamp [UCT]: 2023-12-10 17:03:48 Age [y:d:h:m:s]: 01:156:21:36:29
Block: 910212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373310 RingCT/type: yes/0
Extra: 018e45abbaa727ab99edaa40fca0f8dc5a25fe0fb94bf7fde1cf393f2990b316480211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1cc71aa0ac481a58f9afa60d0bba7cd22644f693ee776e9de757db913ea2228 0.600000000000 1367357 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": 910222, "vin": [ { "gen": { "height": 910212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1cc71aa0ac481a58f9afa60d0bba7cd22644f693ee776e9de757db913ea2228" } } ], "extra": [ 1, 142, 69, 171, 186, 167, 39, 171, 153, 237, 170, 64, 252, 160, 248, 220, 90, 37, 254, 15, 185, 75, 247, 253, 225, 207, 57, 63, 41, 144, 179, 22, 72, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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