Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3796414c83029ceb95a12365f14e0b81764bce8f79d2d3b36e050a0de143e947

Tx prefix hash: df8af0769d7863250120f0c685c4f15acfe5b9f9db59172a65e7d2fec5f3bd46
Tx public key: db7de852b52952d3bb8cd2f233dedc10c23c824565b241b3dc5efef59f0aa0c6
Timestamp: 1723032958 Timestamp [UCT]: 2024-08-07 12:15:58 Age [y:d:h:m:s]: 01:104:01:56:36
Block: 1082700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332871 RingCT/type: yes/0
Extra: 01db7de852b52952d3bb8cd2f233dedc10c23c824565b241b3dc5efef59f0aa0c602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1fb0d6bde9a89f8b8ba7dbcc783a82577e2676f3fef275fcc0889a15a5fd382 0.600000000000 1556531 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": 1082710, "vin": [ { "gen": { "height": 1082700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1fb0d6bde9a89f8b8ba7dbcc783a82577e2676f3fef275fcc0889a15a5fd382" } } ], "extra": [ 1, 219, 125, 232, 82, 181, 41, 82, 211, 187, 140, 210, 242, 51, 222, 220, 16, 194, 60, 130, 69, 101, 178, 65, 179, 220, 94, 254, 245, 159, 10, 160, 198, 2, 17, 0, 0, 0, 1, 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