Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 365fd3f3a9aef20f9eb89e8103022b6a46469c4872762e8762f2152334381c8f

Tx prefix hash: f8fb0416ccb246e1755293ef2668e484d6b156500b8c7d1fec315ccc243a837c
Tx public key: a8d713180fb5ad48fc668ed6fd0a518c058dac20e83850f9495a75a24c1e74c1
Timestamp: 1682855781 Timestamp [UCT]: 2023-04-30 11:56:21 Age [y:d:h:m:s]: 01:275:17:24:29
Block: 749859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458276 RingCT/type: yes/0
Extra: 01a8d713180fb5ad48fc668ed6fd0a518c058dac20e83850f9495a75a24c1e74c1021100000003b3164c24000000000000000000

1 output(s) for total of 2.010972145000 dcy

stealth address amount amount idx
00: 6efc2bdd6eb51060effd73150483ca81979ec5b5a25ac8729e66f125f8fb7d43 2.010972145000 1197876 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": 749869, "vin": [ { "gen": { "height": 749859 } } ], "vout": [ { "amount": 2010972145, "target": { "key": "6efc2bdd6eb51060effd73150483ca81979ec5b5a25ac8729e66f125f8fb7d43" } } ], "extra": [ 1, 168, 215, 19, 24, 15, 181, 173, 72, 252, 102, 142, 214, 253, 10, 81, 140, 5, 141, 172, 32, 232, 56, 80, 249, 73, 90, 117, 162, 76, 30, 116, 193, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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