Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e6a620dbd75c51fe9c70ce9a94e08255b573d0a35f474834641a16c4f445fc5

Tx prefix hash: c0bae15caedb6df92b450e79b91d521f96bcc1523350b9c4b52acbc7ea9130b2
Tx public key: bf03973086bf3c256f259dc6e28a373604f8a7666dd67b4e7a69ba9105beca01
Timestamp: 1735552817 Timestamp [UCT]: 2024-12-30 10:00:17 Age [y:d:h:m:s]: 00:350:00:04:50
Block: 1186355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247709 RingCT/type: yes/0
Extra: 01bf03973086bf3c256f259dc6e28a373604f8a7666dd67b4e7a69ba9105beca01021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6906f45bcba2e6169c78f3fdcecf4413305cec6da13c5ee9fd4656236cbdc2a 0.600000000000 1672834 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": 1186365, "vin": [ { "gen": { "height": 1186355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6906f45bcba2e6169c78f3fdcecf4413305cec6da13c5ee9fd4656236cbdc2a" } } ], "extra": [ 1, 191, 3, 151, 48, 134, 191, 60, 37, 111, 37, 157, 198, 226, 138, 55, 54, 4, 248, 167, 102, 109, 214, 123, 78, 122, 105, 186, 145, 5, 190, 202, 1, 2, 17, 0, 0, 0, 4, 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