Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02a8017aede3cf5342a0adca036ff06baaad8497b5d2c340797ede7254855e1a

Tx prefix hash: ac3a087eb8074ca140a4dcb2b7c138ebfea60a71bafadf24b617fa1137f6d75b
Tx public key: 333a7f27984443199aa72c29078e3c89088ee0f4e1396116d5440c221b1c1b99
Timestamp: 1714887150 Timestamp [UCT]: 2024-05-05 05:32:30 Age [y:d:h:m:s]: 00:333:08:01:26
Block: 1015179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238261 RingCT/type: yes/0
Extra: 01333a7f27984443199aa72c29078e3c89088ee0f4e1396116d5440c221b1c1b9902110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6530fbaa53ea4f93a599d996a61a56a6f0b8b6c7c9a354e01426868fc38e1d62 0.600000000000 1478470 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": 1015189, "vin": [ { "gen": { "height": 1015179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6530fbaa53ea4f93a599d996a61a56a6f0b8b6c7c9a354e01426868fc38e1d62" } } ], "extra": [ 1, 51, 58, 127, 39, 152, 68, 67, 25, 154, 167, 44, 41, 7, 142, 60, 137, 8, 142, 224, 244, 225, 57, 97, 22, 213, 68, 12, 34, 27, 28, 27, 153, 2, 17, 0, 0, 0, 6, 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