Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08f10f04c40ceef6e0a40a1dae4191f6f80e21c8c43575f6b28d4f056c460036

Tx prefix hash: 4b4409d19147e0a6ab590b0e89a75d8dd7c7e7e161c0835e909815b72179cb19
Tx public key: 76bc8244fae5c41d4859ead357a74d97f9ed78273921e67b4b2e0f3df54617e2
Timestamp: 1706033373 Timestamp [UCT]: 2024-01-23 18:09:33 Age [y:d:h:m:s]: 01:087:15:29:23
Block: 941734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323746 RingCT/type: yes/0
Extra: 0176bc8244fae5c41d4859ead357a74d97f9ed78273921e67b4b2e0f3df54617e20211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a663be681ee664d6c4cbe47c628e768af6022b578abc0395069127e60793856b 0.600000000000 1399890 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": 941744, "vin": [ { "gen": { "height": 941734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a663be681ee664d6c4cbe47c628e768af6022b578abc0395069127e60793856b" } } ], "extra": [ 1, 118, 188, 130, 68, 250, 229, 196, 29, 72, 89, 234, 211, 87, 167, 77, 151, 249, 237, 120, 39, 57, 33, 230, 123, 75, 46, 15, 61, 245, 70, 23, 226, 2, 17, 0, 0, 0, 3, 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