Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0024b8e930d5fd3e3dd3eee66d43df86dbbde1e7b2a202db072f38ea2f5a70b7

Tx prefix hash: 567b744760f3b3922633a98e9e605102915eb345a1c7aaf6ee0a2fa2bb4bda0c
Tx public key: 74db45195aedee4999f7f2c077ecfd0d7ecf1e633cb6b27914151613208b0baf
Timestamp: 1634620342 Timestamp [UCT]: 2021-10-19 05:12:22 Age [y:d:h:m:s]: 03:111:16:36:51
Block: 355969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 857670 RingCT/type: yes/0
Extra: 0174db45195aedee4999f7f2c077ecfd0d7ecf1e633cb6b27914151613208b0baf0211000000153fc41461000000000000000000

1 output(s) for total of 40.600122887000 dcy

stealth address amount amount idx
00: 6c6df2e349a4feb015e707cbddea9dce8905c3f63848545f0c4e61f34eca4177 40.600122887000 726495 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": 355979, "vin": [ { "gen": { "height": 355969 } } ], "vout": [ { "amount": 40600122887, "target": { "key": "6c6df2e349a4feb015e707cbddea9dce8905c3f63848545f0c4e61f34eca4177" } } ], "extra": [ 1, 116, 219, 69, 25, 90, 237, 238, 73, 153, 247, 242, 192, 119, 236, 253, 13, 126, 207, 30, 99, 60, 182, 178, 121, 20, 21, 22, 19, 32, 139, 11, 175, 2, 17, 0, 0, 0, 21, 63, 196, 20, 97, 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