Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2faa1512b84b6b312248be9f22dc03fe3b85ec95b56929b7544ec50a020e4039

Tx prefix hash: 78c9033e9e001922dd8cf1fd1a29abc85a022d6235fc60b95ae14a5845b0fd8e
Tx public key: 708eec8f45cf4019050aab158e818621a64d10c0eaef6912170745fca1a9479b
Timestamp: 1578234208 Timestamp [UCT]: 2020-01-05 14:23:28 Age [y:d:h:m:s]: 04:359:06:38:54
Block: 39246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146011 RingCT/type: yes/0
Extra: 01708eec8f45cf4019050aab158e818621a64d10c0eaef6912170745fca1a9479b021100000004d81c26c0000000000000000000

1 output(s) for total of 454.971706771000 dcy

stealth address amount amount idx
00: 3035b5db8358ed8a0271b7ea43ef42da40c8ec1fd77b2cca2937ce1ac8a79b36 454.971706771000 67522 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": 39256, "vin": [ { "gen": { "height": 39246 } } ], "vout": [ { "amount": 454971706771, "target": { "key": "3035b5db8358ed8a0271b7ea43ef42da40c8ec1fd77b2cca2937ce1ac8a79b36" } } ], "extra": [ 1, 112, 142, 236, 143, 69, 207, 64, 25, 5, 10, 171, 21, 142, 129, 134, 33, 166, 77, 16, 192, 234, 239, 105, 18, 23, 7, 69, 252, 161, 169, 71, 155, 2, 17, 0, 0, 0, 4, 216, 28, 38, 192, 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