Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4471f6e2e655440c85f3acf1bbc704bd03cd0699fb4a17f55d9667ebcb34c63

Tx prefix hash: 90a0ff9f3afcdec6999fdb0268ce4a864e6d445b5ed1e1a36448b6690065c9e7
Tx public key: 5b49f3837cd048c939e796e6d2b98d374ddbc833f7532ced1d7041ce553c1492
Timestamp: 1706662037 Timestamp [UCT]: 2024-01-31 00:47:17 Age [y:d:h:m:s]: 01:066:21:14:52
Block: 946958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308868 RingCT/type: yes/0
Extra: 015b49f3837cd048c939e796e6d2b98d374ddbc833f7532ced1d7041ce553c149202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03960bd7ab4102ffe022c5f8bb7861ad6e300403c2a4ae31b8120db8b6459d8f 0.600000000000 1405304 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": 946968, "vin": [ { "gen": { "height": 946958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03960bd7ab4102ffe022c5f8bb7861ad6e300403c2a4ae31b8120db8b6459d8f" } } ], "extra": [ 1, 91, 73, 243, 131, 124, 208, 72, 201, 57, 231, 150, 230, 210, 185, 141, 55, 77, 219, 200, 51, 247, 83, 44, 237, 29, 112, 65, 206, 85, 60, 20, 146, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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