Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0437ed48a62f78c278e1121906926ca0f561778fe47dc07caac3bbc3b5eae5c7

Tx prefix hash: c55e93a46adddcf127d9457400cf6a0cb8b3c9d903534f8fcfaafc82cc3fb629
Tx public key: 7cf4152c896845b875124fa313e52bf6555c9aa28ec3fc776d14f708f3f5d41a
Timestamp: 1733996260 Timestamp [UCT]: 2024-12-12 09:37:40 Age [y:d:h:m:s]: 00:115:01:18:30
Block: 1173505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82003 RingCT/type: yes/0
Extra: 017cf4152c896845b875124fa313e52bf6555c9aa28ec3fc776d14f708f3f5d41a021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73b1f5918d33a11214e0b01d354542631b4b054c5a2dfba10744bc2fdbb89d4e 0.600000000000 1659536 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": 1173515, "vin": [ { "gen": { "height": 1173505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73b1f5918d33a11214e0b01d354542631b4b054c5a2dfba10744bc2fdbb89d4e" } } ], "extra": [ 1, 124, 244, 21, 44, 137, 104, 69, 184, 117, 18, 79, 163, 19, 229, 43, 246, 85, 92, 154, 162, 142, 195, 252, 119, 109, 20, 247, 8, 243, 245, 212, 26, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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