Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7435cc1c80123a33f021ea0a96021b1e137818d7faad43367aa7dcc91fc5cd3c

Tx prefix hash: b5a46c1434041d1e4d800511e2e8a7ba58e23c5921c2eb5e4dc98271a06c0408
Tx public key: a0c067ebd977567d3d32898bf3c935c91bdccf14e2c78843c6062e779b3c008c
Timestamp: 1698840847 Timestamp [UCT]: 2023-11-01 12:14:07 Age [y:d:h:m:s]: 01:120:09:43:58
Block: 882343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347020 RingCT/type: yes/0
Extra: 01a0c067ebd977567d3d32898bf3c935c91bdccf14e2c78843c6062e779b3c008c0211000000054b8f5122000000000000000000

1 output(s) for total of 0.731865664000 dcy

stealth address amount amount idx
00: f1c7fd90c9d63097dc92ff6aefc9a57def3e5b0fa0c23a486754d0c52aba7e14 0.731865664000 1337999 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": 882353, "vin": [ { "gen": { "height": 882343 } } ], "vout": [ { "amount": 731865664, "target": { "key": "f1c7fd90c9d63097dc92ff6aefc9a57def3e5b0fa0c23a486754d0c52aba7e14" } } ], "extra": [ 1, 160, 192, 103, 235, 217, 119, 86, 125, 61, 50, 137, 139, 243, 201, 53, 201, 27, 220, 207, 20, 226, 199, 136, 67, 198, 6, 46, 119, 155, 60, 0, 140, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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