Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 941b1b9cecb54c073252fd430b48ad944d244f52fc10f72584e6f34c41de5149

Tx prefix hash: 1b3ad898314ce7e8b729b2a7d9459b08486226e926f1a938710f20385d7cd7cd
Tx public key: 270a82634a35b8fb42b7a7c92f925675f961eab787781b44eda215ace60050c9
Timestamp: 1696070743 Timestamp [UCT]: 2023-09-30 10:45:43 Age [y:d:h:m:s]: 01:148:03:49:10
Block: 859379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366897 RingCT/type: yes/0
Extra: 01270a82634a35b8fb42b7a7c92f925675f961eab787781b44eda215ace60050c902110000000b4b8f5122000000000000000000

1 output(s) for total of 0.872008404000 dcy

stealth address amount amount idx
00: 17f4f99318828529179cc0a4e19f18c43cbd551e2eaca3865b50358de470ce99 0.872008404000 1313603 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 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": 859389, "vin": [ { "gen": { "height": 859379 } } ], "vout": [ { "amount": 872008404, "target": { "key": "17f4f99318828529179cc0a4e19f18c43cbd551e2eaca3865b50358de470ce99" } } ], "extra": [ 1, 39, 10, 130, 99, 74, 53, 184, 251, 66, 183, 167, 201, 47, 146, 86, 117, 249, 97, 234, 183, 135, 120, 27, 68, 237, 162, 21, 172, 230, 0, 80, 201, 2, 17, 0, 0, 0, 11, 75, 143, 81, 34, 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