Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 513437ab26bdba7aca798cfbd59c884b8d7bd0e6ae945532fd1959e86a0e37cb

Tx prefix hash: 6b7117515548e0548b6ceab3e3e8eafa60f33cce9cc9aa02b0b5f9c79b5d2ebe
Tx public key: 9099b5cb5684cee5e35322706518ca1925d0bc3c01d2a721fef256653ce97f36
Timestamp: 1717292896 Timestamp [UCT]: 2024-06-02 01:48:16 Age [y:d:h:m:s]: 00:304:22:43:09
Block: 1035118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217917 RingCT/type: yes/0
Extra: 019099b5cb5684cee5e35322706518ca1925d0bc3c01d2a721fef256653ce97f36021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8f060c56ead062e2e1c0bacb87073837008ea25d1051d1d8e24002cb95a24e6 0.600000000000 1503637 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": 1035128, "vin": [ { "gen": { "height": 1035118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8f060c56ead062e2e1c0bacb87073837008ea25d1051d1d8e24002cb95a24e6" } } ], "extra": [ 1, 144, 153, 181, 203, 86, 132, 206, 229, 227, 83, 34, 112, 101, 24, 202, 25, 37, 208, 188, 60, 1, 210, 167, 33, 254, 242, 86, 101, 60, 233, 127, 54, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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