Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d49d8b5dcc9f25f251fb67321bec617bd0145834134a8565a69b7bfd00c37889

Tx prefix hash: 83d020d9a81a258bd5b985dbecac7d204a75cf01892c0954b5aab702b6895267
Tx public key: 54ed063c8f864cc7f2dbc242b26ba46f1aed212c1406431a33546a1d7400f5b6
Timestamp: 1722036355 Timestamp [UCT]: 2024-07-26 23:25:55 Age [y:d:h:m:s]: 01:104:03:16:32
Block: 1074429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332929 RingCT/type: yes/0
Extra: 0154ed063c8f864cc7f2dbc242b26ba46f1aed212c1406431a33546a1d7400f5b602110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 568f290929a7cf7cd2281b2666f0529fb5f8c7015e959e6f6532d3d41252bdaa 0.600000000000 1546942 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": 1074439, "vin": [ { "gen": { "height": 1074429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "568f290929a7cf7cd2281b2666f0529fb5f8c7015e959e6f6532d3d41252bdaa" } } ], "extra": [ 1, 84, 237, 6, 60, 143, 134, 76, 199, 242, 219, 194, 66, 178, 107, 164, 111, 26, 237, 33, 44, 20, 6, 67, 26, 51, 84, 106, 29, 116, 0, 245, 182, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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