Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a46c457bd2577d1830b9802c4273e3f867edf57264eee4ec135fcf63e5c33e6e

Tx prefix hash: 10e69fa377ac761943274896d2b80fd7bfe67919f06e6d1e91a4d7a747f6b1e8
Tx public key: 9fd8a8e4eca25ca8e2f924353687ecea32ec1bf8a5260d364bb91035f18f7119
Timestamp: 1728731248 Timestamp [UCT]: 2024-10-12 11:07:28 Age [y:d:h:m:s]: 00:042:23:52:34
Block: 1129944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30696 RingCT/type: yes/0
Extra: 019fd8a8e4eca25ca8e2f924353687ecea32ec1bf8a5260d364bb91035f18f7119021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29c1c45126cce0fe61491f52ea981bccdcd0639edf5b7d428e0ae2b271a40d88 0.600000000000 1612815 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": 1129954, "vin": [ { "gen": { "height": 1129944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29c1c45126cce0fe61491f52ea981bccdcd0639edf5b7d428e0ae2b271a40d88" } } ], "extra": [ 1, 159, 216, 168, 228, 236, 162, 92, 168, 226, 249, 36, 53, 54, 135, 236, 234, 50, 236, 27, 248, 165, 38, 13, 54, 75, 185, 16, 53, 241, 143, 113, 25, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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