Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beaa8155f9d37577b4c63b012ac0f6d439816346225dd54daae96ca7aa90a4b1

Tx prefix hash: b1c5bee4b569c88fb3be076b416923d63992fa5a6984f8a6e99db64772032c73
Tx public key: 1732d601da5a034cc28e7798b759a5b5c57e926c66f786d33cef5176207e1aae
Timestamp: 1736915835 Timestamp [UCT]: 2025-01-15 04:37:15 Age [y:d:h:m:s]: 00:306:13:14:58
Block: 1197644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216606 RingCT/type: yes/0
Extra: 011732d601da5a034cc28e7798b759a5b5c57e926c66f786d33cef5176207e1aae021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe4c4b7b2a1bfbb96f42ecdd6ba732dd9f578cf847949c36346cc609da4839c9 0.600000000000 1684257 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": 1197654, "vin": [ { "gen": { "height": 1197644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe4c4b7b2a1bfbb96f42ecdd6ba732dd9f578cf847949c36346cc609da4839c9" } } ], "extra": [ 1, 23, 50, 214, 1, 218, 90, 3, 76, 194, 142, 119, 152, 183, 89, 165, 181, 197, 126, 146, 108, 102, 247, 134, 211, 60, 239, 81, 118, 32, 126, 26, 174, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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