Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98e632ed0a887484b34afcd3ad3acedc259671f0eb959723f548e5601758831e

Tx prefix hash: 7bca6a9dfe5e7a45713b2b3258d2c1e0684718b2866ae3989bd10e86a7b655e1
Tx public key: dc5b0a1ff93d82d62857272db65fa1796a077e9f634b324aeab6ad383d075010
Timestamp: 1661216837 Timestamp [UCT]: 2022-08-23 01:07:17 Age [y:d:h:m:s]: 03:121:17:06:53
Block: 571746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 866859 RingCT/type: yes/0
Extra: 01dc5b0a1ff93d82d62857272db65fa1796a077e9f634b324aeab6ad383d075010021100000001e6d27f9c000000000000000000

1 output(s) for total of 7.826512070000 dcy

stealth address amount amount idx
00: f54f547889a9d80eae83d6e8863843c4393853ddf962e251c111d49543d07670 7.826512070000 1004970 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": 571756, "vin": [ { "gen": { "height": 571746 } } ], "vout": [ { "amount": 7826512070, "target": { "key": "f54f547889a9d80eae83d6e8863843c4393853ddf962e251c111d49543d07670" } } ], "extra": [ 1, 220, 91, 10, 31, 249, 61, 130, 214, 40, 87, 39, 45, 182, 95, 161, 121, 106, 7, 126, 159, 99, 75, 50, 74, 234, 182, 173, 56, 61, 7, 80, 16, 2, 17, 0, 0, 0, 1, 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