Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcffca1644bd0f7298bd0799c14c8aa23421e9e217c7a17c0abffcb560721977

Tx prefix hash: 4687e70c11d2a979d0c5319624c02124082b8024f79228ee16bc5d4bbf77a5f2
Tx public key: f0745272040512d58f50e6dd47b09c22fd4b3bef8268df33eaf318574e9dd03d
Timestamp: 1723451895 Timestamp [UCT]: 2024-08-12 08:38:15 Age [y:d:h:m:s]: 00:290:09:15:49
Block: 1086177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207462 RingCT/type: yes/0
Extra: 01f0745272040512d58f50e6dd47b09c22fd4b3bef8268df33eaf318574e9dd03d02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1dcf3cb4b83ff289d1119963319e9c18f6b609526b13d20c3ae79288d2aa4775 0.600000000000 1560770 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": 1086187, "vin": [ { "gen": { "height": 1086177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1dcf3cb4b83ff289d1119963319e9c18f6b609526b13d20c3ae79288d2aa4775" } } ], "extra": [ 1, 240, 116, 82, 114, 4, 5, 18, 213, 143, 80, 230, 221, 71, 176, 156, 34, 253, 75, 59, 239, 130, 104, 223, 51, 234, 243, 24, 87, 78, 157, 208, 61, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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