Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f32d76bec781f493727c5718128d9764da9da079b21125f05d72110b5534c5ff

Tx prefix hash: 59abca7d649555549d325d491b7675420d48cc1d8b544d32716d39fce906dbeb
Tx public key: c9bbb94c610c0f42545d906c06861a380159a9a7b6aa542e59b4f5473dc74e25
Timestamp: 1639054023 Timestamp [UTC]: 2021-12-09 12:47:03 Age [y:d:h:m:s]: 04:056:10:09:49
Block: 391780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1077579 RingCT/type: yes/0
Extra: 01c9bbb94c610c0f42545d906c06861a380159a9a7b6aa542e59b4f5473dc74e250211000000034a0f5013000000000000000000

1 output(s) for total of 0.030893747158 xmr

stealth address amount amount idx tag
00: cf0920ee89369aaecdb24ea01bbfe77c80fb4cd196e4cc780f7c20f98a428d84 0.030893747158 788355 of 0 -

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 dinastycoin-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": 391790, "vin": [ { "gen": { "height": 391780 } } ], "vout": [ { "amount": 30893747158, "target": { "key": "cf0920ee89369aaecdb24ea01bbfe77c80fb4cd196e4cc780f7c20f98a428d84" } } ], "extra": [ 1, 201, 187, 185, 76, 97, 12, 15, 66, 84, 93, 144, 108, 6, 134, 26, 56, 1, 89, 169, 167, 182, 170, 84, 46, 89, 180, 245, 71, 61, 199, 78, 37, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369