Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c705f59015497a57010eb2cb6fecf1e9218655892a2663262e7a60df315bdd27

Tx prefix hash: abb93d0517774d1a79dbae48836af5d04756ffafd5288f75c588e68dcb95c389
Tx public key: 8f84fbd3a8585e8cb63b9b11abbee4f889c1505c3718973c8df668571f8edc2b
Timestamp: 1700708927 Timestamp [UCT]: 2023-11-23 03:08:47 Age [y:d:h:m:s]: 01:003:00:16:50
Block: 897619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263514 RingCT/type: yes/0
Extra: 018f84fbd3a8585e8cb63b9b11abbee4f889c1505c3718973c8df668571f8edc2b02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.651351804000 dcy

stealth address amount amount idx
00: fb9b557abc52118d8855f59d8fc962f316e8e048a45139ee631a69ca082bbd18 0.651351804000 1354000 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": 897629, "vin": [ { "gen": { "height": 897619 } } ], "vout": [ { "amount": 651351804, "target": { "key": "fb9b557abc52118d8855f59d8fc962f316e8e048a45139ee631a69ca082bbd18" } } ], "extra": [ 1, 143, 132, 251, 211, 168, 88, 94, 140, 182, 59, 155, 17, 171, 190, 228, 248, 137, 193, 80, 92, 55, 24, 151, 60, 141, 246, 104, 87, 31, 142, 220, 43, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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