Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8fdb5c1c9308d75ca70d7cbfa769340527318b67f0d07412e63b8923467bd72

Tx prefix hash: 64dcb55768cbe3948cdf623608f0094128418fa66969891f5b081a19fd998ca4
Tx public key: 44f76195b266a359886a2fbd4b769f720336bb06c0c2e5a5329f9fd94c6c5c84
Timestamp: 1707808796 Timestamp [UCT]: 2024-02-13 07:19:56 Age [y:d:h:m:s]: 00:335:09:53:22
Block: 956476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240125 RingCT/type: yes/0
Extra: 0144f76195b266a359886a2fbd4b769f720336bb06c0c2e5a5329f9fd94c6c5c840211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18f34da86d677e9422318571f1e2afefdf9c64a27330c6469a9e9e1609e486c8 0.600000000000 1415784 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": 956486, "vin": [ { "gen": { "height": 956476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18f34da86d677e9422318571f1e2afefdf9c64a27330c6469a9e9e1609e486c8" } } ], "extra": [ 1, 68, 247, 97, 149, 178, 102, 163, 89, 136, 106, 47, 189, 75, 118, 159, 114, 3, 54, 187, 6, 192, 194, 229, 165, 50, 159, 159, 217, 76, 108, 92, 132, 2, 17, 0, 0, 0, 5, 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