Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b524013dfea21de15c8424186961b7a32d275ae5e18fce36803f367374b5970e

Tx prefix hash: fa2fb8b0c59d5beb2d2cea56a1be9ff0a31b4793246419e60f880c3575e88809
Tx public key: 7f5b097cb791e4fa519e34cff4d862590c130a0d59c82726e30923fe6bfb0540
Timestamp: 1672636706 Timestamp [UCT]: 2023-01-02 05:18:26 Age [y:d:h:m:s]: 02:148:18:30:31
Block: 665747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 628070 RingCT/type: yes/0
Extra: 017f5b097cb791e4fa519e34cff4d862590c130a0d59c82726e30923fe6bfb054002110000000252542ceb000000000000000000

1 output(s) for total of 3.820355588000 dcy

stealth address amount amount idx
00: 4d78e4f27a7a876d56c6fd4d30eb81c9f5488034b6ab09e71e38d9ee6020d64d 3.820355588000 1106806 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": 665757, "vin": [ { "gen": { "height": 665747 } } ], "vout": [ { "amount": 3820355588, "target": { "key": "4d78e4f27a7a876d56c6fd4d30eb81c9f5488034b6ab09e71e38d9ee6020d64d" } } ], "extra": [ 1, 127, 91, 9, 124, 183, 145, 228, 250, 81, 158, 52, 207, 244, 216, 98, 89, 12, 19, 10, 13, 89, 200, 39, 38, 227, 9, 35, 254, 107, 251, 5, 64, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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