Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395915bed9558128b42fd08ffca3874d4522bb18aec74cc61460ff3121b90aea

Tx prefix hash: c6dd920b033dc4fb5cfa77e4ef94e057ea5e310c69c0bf840a1b57c805d0afd0
Tx public key: 792c35869336384818d6f5def238e8ebaec5b094fc35fb31fe448d2deb638b66
Timestamp: 1636703588 Timestamp [UCT]: 2021-11-12 07:53:08 Age [y:d:h:m:s]: 03:122:23:04:01
Block: 372660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 866290 RingCT/type: yes/0
Extra: 01792c35869336384818d6f5def238e8ebaec5b094fc35fb31fe448d2deb638b6602110000000c328bb496000000000000000000

1 output(s) for total of 35.745642853000 dcy

stealth address amount amount idx
00: 13f55cdbb1d9bebc2b2cc932076d4dc8d9f5523e4fd74240280939de5f82ec75 35.745642853000 754842 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": 372670, "vin": [ { "gen": { "height": 372660 } } ], "vout": [ { "amount": 35745642853, "target": { "key": "13f55cdbb1d9bebc2b2cc932076d4dc8d9f5523e4fd74240280939de5f82ec75" } } ], "extra": [ 1, 121, 44, 53, 134, 147, 54, 56, 72, 24, 214, 245, 222, 242, 56, 232, 235, 174, 197, 176, 148, 252, 53, 251, 49, 254, 68, 141, 45, 235, 99, 139, 102, 2, 17, 0, 0, 0, 12, 50, 139, 180, 150, 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