Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351a7845d8746448aa6bdc6423da041e43c5bf3f4c7ac2e4baeb0c67e92dcf1d

Tx prefix hash: 8f5f2160dc6a1be3b2034f2ae95d15ffca9a61a663387831bddf682cfd157579
Tx public key: e7b3147e86a50031d3759218ac69901535ce3c112745537fdce6d696f29fd102
Timestamp: 1682165648 Timestamp [UCT]: 2023-04-22 12:14:08 Age [y:d:h:m:s]: 01:264:18:35:01
Block: 744136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450724 RingCT/type: yes/0
Extra: 01e7b3147e86a50031d3759218ac69901535ce3c112745537fdce6d696f29fd102021100000005e6d27f9c000000000000000000

1 output(s) for total of 2.100722747000 dcy

stealth address amount amount idx
00: f5374e89358cdc71d8f5e1c7c5cfe2d521bb634fd06053d1ff71d62f9bfd5ce6 2.100722747000 1191393 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": 744146, "vin": [ { "gen": { "height": 744136 } } ], "vout": [ { "amount": 2100722747, "target": { "key": "f5374e89358cdc71d8f5e1c7c5cfe2d521bb634fd06053d1ff71d62f9bfd5ce6" } } ], "extra": [ 1, 231, 179, 20, 126, 134, 165, 0, 49, 211, 117, 146, 24, 172, 105, 144, 21, 53, 206, 60, 17, 39, 69, 83, 127, 220, 230, 214, 150, 242, 159, 209, 2, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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