Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3515e9ee2eca0b2d5f8c44708494018a1e7c03dbac7a4a11a9a916b67a6bd78c

Tx prefix hash: 23ab297515b79cfd7934c5f60a7accfd69ef595432c8dc1c73164bcfad3968d0
Tx public key: 65199da64fca76daabe463ec310e5f7a1f2b56646e71d3a419cf1e6b89a919b6
Timestamp: 1727559583 Timestamp [UCT]: 2024-09-28 21:39:43 Age [y:d:h:m:s]: 00:166:21:38:00
Block: 1120231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119096 RingCT/type: yes/0
Extra: 0165199da64fca76daabe463ec310e5f7a1f2b56646e71d3a419cf1e6b89a919b6021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f374564920bba44a6bc62d0aba3e5f12e6ec3236cfa4ef62aba2842829645f5b 0.600000000000 1602072 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": 1120241, "vin": [ { "gen": { "height": 1120231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f374564920bba44a6bc62d0aba3e5f12e6ec3236cfa4ef62aba2842829645f5b" } } ], "extra": [ 1, 101, 25, 157, 166, 79, 202, 118, 218, 171, 228, 99, 236, 49, 14, 95, 122, 31, 43, 86, 100, 110, 113, 211, 164, 25, 207, 30, 107, 137, 169, 25, 182, 2, 17, 0, 0, 0, 5, 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