Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbebb312450a3e4b7f792f87c573cea1a1a1a8a300abdda17615ba9637f953dd

Tx prefix hash: 001e0fdc004959f3272f2dacb986b362f429dcf563da85cb866695587b9200d1
Tx public key: 32b8154e8c4398543f7d2d17db9e95228f3a7978c0fda71b3e473bf17da69363
Timestamp: 1711248418 Timestamp [UCT]: 2024-03-24 02:46:58 Age [y:d:h:m:s]: 01:199:02:03:28
Block: 985023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400924 RingCT/type: yes/0
Extra: 0132b8154e8c4398543f7d2d17db9e95228f3a7978c0fda71b3e473bf17da693630211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df68dfdf95e931bf03667e56c7df5104a81ca5b8941d74b19b1e4171cfe0b074 0.600000000000 1445228 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": 985033, "vin": [ { "gen": { "height": 985023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df68dfdf95e931bf03667e56c7df5104a81ca5b8941d74b19b1e4171cfe0b074" } } ], "extra": [ 1, 50, 184, 21, 78, 140, 67, 152, 84, 63, 125, 45, 23, 219, 158, 149, 34, 143, 58, 121, 120, 192, 253, 167, 27, 62, 71, 59, 241, 125, 166, 147, 99, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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