Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cc54b1878b1bdf1faf2d632168224a854b3cf1d1068c52dc7abed273ac9f3de

Tx prefix hash: f03e8839f751b6310ba7249e02a65b4362f79e3276ca5c1eb57c4eb9cbc031bc
Tx public key: 27dc6a54f7dc7e0d497592dedc291c7173726bbba260796ac10e695f17de5b58
Timestamp: 1676399800 Timestamp [UCT]: 2023-02-14 18:36:40 Age [y:d:h:m:s]: 01:264:10:14:08
Block: 696989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449864 RingCT/type: yes/0
Extra: 0127dc6a54f7dc7e0d497592dedc291c7173726bbba260796ac10e695f17de5b5802110000000d835e4d22000000000000000000

1 output(s) for total of 3.010135370000 dcy

stealth address amount amount idx
00: f5d1b09b76b824d3da4d77b7351e278a9fa351a350ff91bbe73ad510dfbda6c9 3.010135370000 1140052 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": 696999, "vin": [ { "gen": { "height": 696989 } } ], "vout": [ { "amount": 3010135370, "target": { "key": "f5d1b09b76b824d3da4d77b7351e278a9fa351a350ff91bbe73ad510dfbda6c9" } } ], "extra": [ 1, 39, 220, 106, 84, 247, 220, 126, 13, 73, 117, 146, 222, 220, 41, 28, 113, 115, 114, 107, 187, 162, 96, 121, 106, 193, 14, 105, 95, 23, 222, 91, 88, 2, 17, 0, 0, 0, 13, 131, 94, 77, 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