Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 974bb1fad78c35cad987c06fd74462f658e16083c82180a2fc233c1073135c0f

Tx prefix hash: a115d08f6959104de85173301f753568896e2dd426396efc76ae5aec7b83e625
Tx public key: adb0c3e70f2e0f8d35f11eddc2892f90ce80a9e6ade0a4c78fc7e7a2b2afb4b5
Timestamp: 1580972508 Timestamp [UCT]: 2020-02-06 07:01:48 Age [y:d:h:m:s]: 04:324:13:12:47
Block: 59491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123612 RingCT/type: yes/0
Extra: 01adb0c3e70f2e0f8d35f11eddc2892f90ce80a9e6ade0a4c78fc7e7a2b2afb4b502110000000103d36d11000000000000000000

1 output(s) for total of 389.836446991000 dcy

stealth address amount amount idx
00: 0592f0ca467a45ec848f5c432a86dce13f8e7df261dacf07d7f6ceea5ad389e1 389.836446991000 109890 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": 59501, "vin": [ { "gen": { "height": 59491 } } ], "vout": [ { "amount": 389836446991, "target": { "key": "0592f0ca467a45ec848f5c432a86dce13f8e7df261dacf07d7f6ceea5ad389e1" } } ], "extra": [ 1, 173, 176, 195, 231, 15, 46, 15, 141, 53, 241, 30, 221, 194, 137, 47, 144, 206, 128, 169, 230, 173, 224, 164, 199, 143, 199, 231, 162, 178, 175, 180, 181, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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