Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f15a2803ea37877157a0a79bbc883b20ebc91eebb82b8bc3de5683d244507d8c

Tx prefix hash: 0ebab4207a981b7d8f1c3363391f052a00cb51f12720d490779f302131839e18
Tx public key: ac3e19f7de4cb3bb7bfa110ce8392aa32103aa3d30f50eddddfd71e4d8945b24
Timestamp: 1707581917 Timestamp [UCT]: 2024-02-10 16:18:37 Age [y:d:h:m:s]: 01:092:02:04:13
Block: 954593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326886 RingCT/type: yes/0
Extra: 01ac3e19f7de4cb3bb7bfa110ce8392aa32103aa3d30f50eddddfd71e4d8945b2402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ac395ab8b16a48c0f3fd34051a460a3e4ff3740a8649e0f6d12536d76e1c075 0.600000000000 1413873 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": 954603, "vin": [ { "gen": { "height": 954593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ac395ab8b16a48c0f3fd34051a460a3e4ff3740a8649e0f6d12536d76e1c075" } } ], "extra": [ 1, 172, 62, 25, 247, 222, 76, 179, 187, 123, 250, 17, 12, 232, 57, 42, 163, 33, 3, 170, 61, 48, 245, 14, 221, 221, 253, 113, 228, 216, 148, 91, 36, 2, 17, 0, 0, 0, 1, 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