Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e2076eb68835522e867edc39a5f8ba4f9d237a6f19a4ddc769456877705d120

Tx prefix hash: 3294d6872b0a40789f49f5c49b62bcadd798e4eafa9c67e19b23315a0a50fb2b
Tx public key: b443ed261c0310116e9c12c9723f0967e06c79d5c7d16171fddc8cb04a8b8bb6
Timestamp: 1709084151 Timestamp [UCT]: 2024-02-28 01:35:51 Age [y:d:h:m:s]: 01:092:02:10:05
Block: 967064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326865 RingCT/type: yes/0
Extra: 01b443ed261c0310116e9c12c9723f0967e06c79d5c7d16171fddc8cb04a8b8bb602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0712efd0539832f02b5cf474265f86008a43ffb853efd81685c48a857b7ee93d 0.600000000000 1426835 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": 967074, "vin": [ { "gen": { "height": 967064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0712efd0539832f02b5cf474265f86008a43ffb853efd81685c48a857b7ee93d" } } ], "extra": [ 1, 180, 67, 237, 38, 28, 3, 16, 17, 110, 156, 18, 201, 114, 63, 9, 103, 224, 108, 121, 213, 199, 209, 97, 113, 253, 220, 140, 176, 74, 139, 139, 182, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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